-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closing project crashes MS instance #20692
Comments
Could you please send us diagnostic info (from the diagnostic menu > Save diagnostic file) so we can try and identify what's going on in your specific case? Thanks! |
Sure! Sending now... Really hope this helps, it is quite annoying. 😓 |
@Fristover |
@Fristover were you able to reproduce this crash using a non-portable version? |
Oops, haven't tried it, I surely can reproduce it so I'll try to send the files today. |
oopsbutnotportable.zip |
@Fristover Thank you for the information. From the crash dumps, it is evident where the crash occurs - when deleting mixer objects. Dump file
Could you provide the score on which you are reproducing the crash? The score is needed to understand what mixer objects you are creating and in what quantity. Also, if you have time, could you test this build? (It's a build from a PR that might fix the afore mentioned issue) |
Sure! Here's the last score the issue happened with (though this happens with every score randomly, can't really find a file that reproduces this every time or anything similar, sadly): I'm gonna comment again when I test the mentioned build, hope it works! |
Ok it almost made me think it was fixed on that build but got a crash after many attempts, attaching the diagnostic files and the score just in case it's a different issue: Journey_To_the_Island.mscz.zip |
@Fristover About the new crashes: I notice that the export code doesn't account for this behaviour, and yes, it's a bug that needs fixing. If that's the case, I suggest closing this issue, marking it as a duplicate of #9467, and opening a new one specifically for the active export case, if it doesn't already exist. |
Oh, that's curious, I did start an export but cancelled it, then closed the score a while after the dialog disappeared, didn't think that was the cause, haha. Anyway, glad the main issue is fixed, I guess it's fine to close it. 😁 |
Uuhhhh, it's happening again... 3 times today... Diagnostic files and one of the affected projects here: https://www.dropbox.com/scl/fo/x356lrpw7ya44zi0yn5uo/h?rlkey=zurkprh3bhoava37xxafvz9f0&dl=0 |
Can't reproduce on my side with the attached score.. @Fristover Are you using MuseScore 4.2.1 (Installed version)? |
It's on every score, that's just the last one where it happened until then I am using the installed version of 4.2.1, yes (though the Muse Hub still says there's an update [to the same exact version] and fails every time it tries to install it...) |
Note that #14790, which would fix the crash according to Elnur, has (still) not been merged yet. You can try it out, using these instructions: https://github.com/musescore/MuseScore/wiki/Downloading-and-running-test-builds#downloading-builds-from-pull-requests |
@cbjeukendrup Tested. I left a comment in PR |
It's been happening a lot recently (noticed today), will leave the file here just in case... I should mention I only have one instance open. |
Issue type
Crash or freeze
Bug description
Sometimes, when you close a project, the currently running MS instance crashes instead of taking you to the home screen, I have not been able to find a pattern on this since it just randomly happens even when not doing any changes to the score.
Doesn't matter how many instances are running, the behavior is exactly the same.
Steps to reproduce
Screenshots/Screen recordings
No response
MuseScore Version
4.2 Release
Regression
No.
Operating system
Windows 11, latest canary build
Additional context
This has been a thing since the first MS4 build I've tried, I thought this was already reported...
(I'll try to update this once I find anything that could be useful, though I haven't found anything for the past year so my expectations are really low)
The text was updated successfully, but these errors were encountered: