CRASH: "Insert Measure After Selection" (results in corrupt file)
Reported version
4.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Inserted two measures after selection and had the following problems:
-
(project is in 4/4) noticed the bar immediately after, visually, had become a 3/4 bar. When interacted with, it returned to 4/4 but the note I clicked turned into a rest.
-
tried to add a double bar line after the extra 2 bars and it wouldn't do it
-
if I selected the 2 bars and hit any note name "ie. C" nothing happened
-
finally I tried selecting a quarter note and clicking on the 2 bars. Musescore crashed immediately. Upon reopening, it said my file was corrupted. Lost 30 minutes of work 😭
| Attachment | Size |
|---|---|
| Screenshot 2023-01-01 at 2.51.02 pm.png | 442.36 KB |
Fix version
4.0.1
Comments
Did the corruption happen in the full score, or in the part scores? To investigate the problem, we need at least the corrupted score.
In reply to Did the corruption happen in… by cbjeukendrup
Part view
Thanks. The good news is that we have a solution (https://github.com/musescore/MuseScore/pull/15257) so that this will not happen again in the next update.
If you would like us to try to fix the corrupted score, feel free to upload it here.
Automatically closed -- issue fixed for 2 weeks with no activity.
In reply to Thanks. The good news is… by cbjeukendrup
In that case, can you please fix this?
(Attachment removed)
See How to fix MuseScore 4 corrupted files
In reply to See How to fix MuseScore 4.0… by Jojo-Schmitz
I have already tried exporting .xml and MuseScore 4 keeps crashing. I've tried the additional solutions with the same result.
Recording: https://rumble.com/v27iopq
In reply to I have already tried… by karolcpm
Please fix. I spent 12+ hours on the project above and would like to know if the bug is easily fixable or I'll have to use a workaround in the meantime.
This bug here got fixed 2 weeks ago and the fix is part of 4.0.1
It may not fix corruptions in pre -4.0.1 scores though
If you can still reproduce this bug, please open a new issue, with sample score and steps to reproduce
In reply to This bug here got fixed 2… by Jojo-Schmitz
Thanks for the reply. I'll consider using your suggestion after completing my project.
In reply to This bug here got fixed 2… by Jojo-Schmitz
I fixed it!!!
I selected the entire score, cut, and pasted several measures past the corrupted measures. Then I used the "Remove selected range" option from the tools menu to delete the corrupted measures. I uploaded to the MuseScore sharing site and it worked!