mltframework / mltframework/shotcut
Freeze on exit (when UI elements on 3rd monitor)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 11h 27m
- Merged PRs (30d)
- 5
Description
I'm having a freeze of the application on exit. Luckily it doesn't cause any save corruption or anything but when I try to close it with the top X or the file-exit. This happened with the previous full release version right before 23.09.29. It wasn't a real problem just annoying. I completely uninstalled the previous version and then reinstalled this one. I even checked the "remove settings from registry".
I do think I was able to isolate the cause though. I have a three monitor setup and I have a second video card running my 3rd monitor. When I move parts of the UI to that 3rd monitor, then it seems to freeze on exit. BUT if I put those elements back onto the main window before closing, then it seems to work fine. I've even attempted to close the dialogs (ex. Filters) on the 3rd monitor but unless I drag it back and reintegrate it with the main then it will freeze on exit. Interestingly enough it closes all the UI elements that are on the other screens and then just hangs on the main UI window. I have to force close it but it doesn't seem to break anything. Well, yet, at least.
Shotcut Version: 23.09.29
Win11 build: 22621.1848
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. First reproduce the exit freeze with UI elements on a third monitor and a separate video card, then compare it with elements reintegrated into the main window; done means the application exits normally in both cases without requiring force close.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100