Crash on save of a score with corrupt parts
Reported version
3.2
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
needs info
Regression
No
Workaround
Yes
Project
I am working on a score, click save, MuseScore3 crashes completely.
It happens frequently also when just editing, but this particular score I now can not even save anymore.
Version is up to date. Tried to save in different places and different formats, same result.
| Attachment | Size |
|---|---|
| It_Don't_Mean_A_Thing.mscz | 42.87 KB |
Comments
Confirmed. The parts for Flöte and Altsaxophon are corrupt, delete and regenerate. Fixed score attached
Now we'd need to know how that corruption happened
In reply to Confirmed. The parts for… by Jojo-Schmitz
How do we find out how it happend? I can only say, that Version 3 crashes pretty frequently. But not usually when saving. That happend yesterday for the first time. Maybe one of those crashes could have done it?
In reply to Confirmed. The parts for… by Jojo-Schmitz
Thank you for the fixed score!
Came up again in #294475: Unable to export and save files and https://musescore.org/en/node/294196
See also #292460: Crash on save of file with corrupt parts, which might be a duplicate
See also #304159: Crash on saving due to corrupt part, with the score from there I couldn't get a current development build to crash (I can though with a self-built one in Debug mode,
Fatal: ASSERT: "first()" in file ...\libmscore\measure.cpp, line 1916). Same with the score from this issue here and the ones from #302021: Crashing Error when Attempting to Save, #300587: Musescore crashing at first attempted edit after opening larger concert band score, #295684: Clicking on playback - crash on save, #294475: Unable to export and save files, #292460: Crash on save of file with corrupt parts and those from https://musescore.org/en/node/294196 and https://musescore.org/en/node/293488Also the scores from https://musescore.org/en/node/305062 and https://musescore.org/en/node/305057
This might be fixed in 3.5 Alpha (Beta expected any day now), in a Release version (in a Debug version it'd still crash, see above)
Mark active again if it still happens with 3.5 (Alpha or later) and attach the score
My guess there will turn out to be other types of scores that crash on save, maybe even some of these will relate to corruption in parts. But the specific issue here - a completely empty measure that happens to be hidden within a multimeasure rest - is definitely fixed. We'd also still love it if anyone who has experienced this can provide any insight into how that might have happened.
482bd50 apparently prevents many of these crashes (it is in all development builds since March, and also in the 3.5 Beta)
As does removing and regenerating the corrupt part.
Still seems to happen though, see #307629: Crashing after tying a whole note chord to the next measure and #307627: Crash after adding tremolo to unpitched staff
Both crash with a failed assertion (in the latest 3.x Debug build, but not in 3.4.2!):
Fatal: ASSERT: "_lidLocalIndices.contains(lid)" in file \libmscore\xml.h, line 276