Crashing Error when Attempting to Save
Reported version
3.4
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
Yes
Project
- open "Mountains"
- either attempt to save the file, or wait long enough (it works with both methods)
- the score would crash and tell me an error had occurred
- note that the workaround listed above does not apply to the original file; I would have to redo the entire score over on a completely new file, which is impractical and inefficient
- the message displayed says 'previous session closed unexpectedly'
- this only began with the new update (version 3.4.2, launched Feb. 7 I believe); I kept putting the update off to work on the score but finally decided to get it after a few days (I started writing this score Feb. 26). After installing, everything ran smoothly until I attempted to save the file.
-
I have tried uninstalling and reinstalling MuseScore with no success.
Mountains.mscz Mountains.mscz Mountains.mscz Mountains.mscz Mountains.mscz Mountains.mscz Mountains.mscz Mountains.mscz Mountains.mscz Mountains.mscz
Attachment | Size |
---|---|
Mountains.mscz | 57.64 KB |
Comments
the message that pops up says 'previous session quit unexpectedly'
This kind of error comes up from time to time. The "solution" is to go to File->Parts..., delete all parts, and then generate them again. Indeed, that works in this case, and it will allow you to save your score without causing the program to crash. I hope you have not spent too much time making adjustments in the individual parts, because all of that work will be lost. With a little detective work, we may be able to figure out what exactly in your score is causing the problem.
See #292064: Crash on save of a score with corrupt parts