Program too unstable
S2 - Critical
Program too unstable. Random things cause the program to crash and files to get corrupted (clicking on a note, adding a note, deleting items, using the selection menu, opening a file, jumping to another measure, whatever)
You need to be more specific, step by step description what to to to get it to crash
I can't be more specific because it can happen at any time for any reason. There is no step-by-step that will trigger the program to close and corrupt the file because what causes it may not cause it; the stepper won't always cause it and you could do something else that will cause it. I only know that it has corrupted me at least 3 files since launch.
After another sudden shutdown just playing, when I open the app I find this.
with a corrupt score anything can happen, crashes included.
In reply to with a corrupt score… by Jojo-Schmitz
Absolutely nothing justifies crashing while opening a corrupt score. If one goes into a library and opens a book with a missing page, it is not like anything can happen, only that there is incoherent information.
The right behaviour upon opening a corrupt score is:
- stop parsing when something cannot be interpeted (or asks for an insane amount of resources)
- open the score with what was correctly read and understood (which can be nothing)
- warn the user that not everything was read
In reply to Absolutely nothing justifies… by prigault
The problem is not opening a corrupted sheet music, it's that Musescore is corrupting files for no apparent reason.
That is known (meanwhile) and in the works, most of these hopefully fixed in the upcomming 4.0.2
Fantastic. Hopefully it gets resolved. The software has dethroned almost everything paid and it is not fair that these failures take steps back.