Fix Log Viewer Freeze and Update to v4.2.10#11
Conversation
- Implemented batch processing limit (100 lines/50ms) in `LogViewerPopup.process_log_queue` to prevent main thread starvation during high-volume log output from `llama.cpp`. - Added robustness checks (`winfo_exists`) and exception handling to the log processing loop. - Updated main application file to `lyrn_sad_v4.2.10.pyw`. - Moved previous version `v4.2.9` to `deprecated/Old/`. - Updated `README.md` and `build_notes.md`.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
Fixed a bug that caused the GUI to freeze if you had the view logs popup open and you loaded a different model. Turned off jobs by default for current test cycle.
1 participant
This change fixes a critical application freeze ("Not Responding") that occurred when offloading or reloading a model while the "View Logs" popup was open. The freeze was caused by the log viewer loop overwhelming the main GUI thread with rapid updates from the model loader's console output.
The fix limits the log viewer to process a maximum of 100 lines per 50ms tick, ensuring the main event loop remains responsive.
This update also bumps the application version to v4.2.10.
PR created automatically by Jules for task 4327715325800030339 started by @bsides230