Crash
Reported version
4.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
PR created
Regression
No
Workaround
Yes
Project
When Ctrl+del the last two bars the client crashes
| Attachment | Size |
|---|---|
| Gubben i lådan.mscz | 66.47 KB |
Comments
I can confirm. Please open an issue on GitHub so the developers can begin investigating.
In reply to I can confirm. Please open… by Marc Sabatella
Is this something i should do? New to the community.
This whole process of using GitHub is new. It's a bit complicated right now but will hopefully get better over time. My personal recommendation is that people report potential bugs here on musesocre.org to make sure the bug is real and reproducible, and then the person who reported it should also open the issue on GitHub, since they are the ones impacted and would be the ones that the developers would need to contact if more details are needed. Ideally, though, there would be a single button to do that. Meanwhile, try this link:
https://github.com/musescore/MuseScore/issues/new?assignees=&labels=&te…
As Marc requested: Please open an issue on GitHub
IMHO though that's too much to ask from mere mortal users (not developers) of a released version (not nightly builds, Alpha, Beta, RC)
In reply to This whole process of using… by Marc Sabatella
Thanks! Lol you should make a report/suggestion about the button.
I don't know if you are interested: On Linux I Inserted a break; Selected the last two Measures and pressed Del then from Properties clicked on the trash can.
In reply to I don't know if you are… by Shoichi
Thanks! Im on windows and made a completley new score with the right amount of bars lol, ill check it out next time.
This seems to be same problem as https://musescore.org/en/node/341414...
Workaround 1: make sure you have added the correct amount of measures and the correct time signatures before opening any of the part scores for the first time (and after opening a part score, don't add/remove measures/timesignatures anymore)
Workaround 2: as you did, create a new score with the right amount of measures, then copy everything from the old score to this new score, and create new part scores in the new score.
Anyway, the good news is that this corruption won't happen again in the next patch release when it's ready, which will include the fix from https://github.com/musescore/MuseScore/pull/15257.