Musescore crashes upon modifying length of certain notes
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
-
Open the score attached below on the newest version of Musescore available.
-
Go to staff 6, measures 31-34
-
Pick any note within that range and attempt to adjust its note length (e.g. from 16th to 8th, quarter to 32nd) using either a button or keyboard shortcut.
Expected result: the notes are adjusted accordingly to the value specified.
Actual result: Musescore crashes.
Workaround: If the notes are deleted and manually re-added, the app no longer crashes when repeating steps 2&3.
I could not figure out how to reproduce this bug from a blank document.
| Attachment | Size |
|---|---|
| Believe in you TV Draft 1.mscz | 1.09 MB |
Comments
I can confirm this, and can see why - the part is corrupt, those measures show as empty in the part but not the score. Also bar 10 looks completely empty in the part, and other corruptions seem apparent as well. So anything you can share about the process by which this part was created could be helpful in reproducing the problem from scratch.
Meanwhile, I recommend removing the part then regenerating it, in File / Parts.
Probably related to #313634: Crashing on adding articulation in a score with linked staves and corrupted part and #139026: Corruptions in (linked) parts get detected, but only reported in the debug output, not in a dialog box like for corrupt scores
My score is doing the same thing. I am editing a pdf that I downloaded from musescore and it crashes about every six notes I edit, especially if I change the length of a note, now it won't even open the file i saved
On my PC MuseScore can't even read/open that score. I can open it with 7Zip though, extract the mscx and open that.
This score is not having parts, so likely an entirely different issue. But one I so far can't reproduce.