Muescore Crashes when adding time signature (on a corrupt score)

• Apr 6, 2022 - 14:13
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
by design
Regression
No
Workaround
No

Trying to change the time signature to 2/4 at measure 64 by dragging it from the palette. The app always crashes. I made it work by changing the measure settings.

Attachment Size
For good.mscz 31.26 KB

Comments

You have corruption in measure 74. Deleting the contents of that measure allows me to change the time signature, though you'll want to review the score before doing that. A lot of measures after 64 are longer than a bar of 4/4 (indicated by the small gray plus sign in the top right of the measure). I'd recommend correcting these measures before changing the time signature, as otherwise you'll end up with some quite nasty durations. To get rid of extra beats in a measure, select the part you want gone and press ctrl+delete (cmd+delete on Mac).

Title Muescore Crashes when adding time signature Muescore Crashes when adding time signature (on a corrupt score)
Frequency Many Once
Status active by design

Basically by design: with a score that contains corruptions anything cxan happen, including crashes