Crashing constantly

• Jun 9, 2020 - 16:08
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
MuseScore

This one keeps crashing again, not sure why though

Attachment Size
Epic_Orchestra_06.mscz 201.87 KB

Comments

• Jun 9, 2020 - 16:16
Severity S4 - Minor ⇒ S2 - Critical
Status duplicate ⇒ active

Seems to be a corrupt Piccolo part (possibly others). Crashes with current 3.5 build too, I thought we had a fix in place for that?

Reply

• Jun 9, 2020 - 16:58

what, the bug or that score?

Fixed score attached, but to fix the bug we'd need to know how to reproduce it
(yes, we can see the crash, but we'd need to know how the score baceme corrupt to begin with)

Attachment Size
Epic_Orchestra_06.mscz 208.52 KB

Reply

• Jun 9, 2020 - 18:56

For the record, it actually does seem this crash is fixed in 3.5, at least in a "release" version. It only crashes for me in my debug version because there is extra code there (an "assert" statement) designed to trigger a crash on this particular corruption so we remember to keep trying to find the underlying cause, but the actual 3.5 won't crash. That includes the Alpha that is already released, and the Beta coming any day now, and of course the final 3.5 whenever that happens.

For the record, you can see the corruption in the original if you go to the Piccolo part and press M to disable multimeasure rests. About eight bars into that last mmrest (after the key change) you'll see a measure that is completely empty (looks like an extra thick barline followed by too much space). There were bugs in older versions that were known to create situations like this, but the most like one #294120: Insert measures in mmrest mode leads to corruption/crash was fixed for 3.3.0, and this particular score was last saved in 3.3.4. So I am not sure what may have happened.

Reply