This score won't open
Can anyone try to open this file? A member of the French forum is having a nervous breakdown, and is about to quit MuseScore. The file doesn't show up corrupted, but it runs in a loop, hangs and crashes. I've looked in the .mscx file, but it's like looking for a needle in a haystack...
This file: La Morte (version 2).mscz
Comments
Crashes MU4 and freezes my Linux...
In reply to Crashes MU4 and freezes my… by Shoichi
Indeed, me too. Linux and Windows11 (I guess MacOs also...)
That's a nasty bug...
In reply to Indeed, me too. Linux and… by cadiz1
3.6.2 (container xml) Fatale errore: linea 2 colonna 11 No definition for element container available.
![25050901.png]( "25050901.png")
2.3.2 " "
There were broken Staff Type change elements.
In reply to There were broken Staff Type… by mercuree
The crash is related to the fact that in the old version of Musescore it was possible to add several StaffTypeChange Elements to one measure.
But since version 4.5 this has been fixed and it is impossible to add several StaffTypeChange elements.
However, the crash was not fixed for old projects that already contained several such elements in one measure.
https://github.com/musescore/MuseScore/issues/25145
In reply to The crash is related to the… by mercuree
Ok, thanks. And this one (I guess another version of the same file): same problem? La Morte.mscz
In reply to Ok, thanks. And this one (I… by cadiz1
La Morte_0_fixed2.mscz
In reply to [inline:La Morte_0_fixed2… by mercuree
Thanks.
In reply to Thanks. by cadiz1
One question though: how did you manage to open these files?
In reply to One question though: how did… by cadiz1
If you search the mscx file for the tag, you will see that there is a measure that contains as many as 3 of them; by deleting 2 of these elements the score opens again. Obviously 'mercuree' already knew what to look for, otherwise, as you said, it was just like looking for a needle in a haystack...
In reply to If you search the mscx file… by ILPEPITO
Tag is: StaffTypeChange
In reply to One question though: how did… by cadiz1
Despite what @ILPEPITO says, I didn't know what was causing the crash in this case at first.
I don't know how to debug C++ applications, so I always follow this principle:
1. First, instruments are removed from the file until the file starts opening.
2. Then only the instrument or staff that causes the crash is left in the file.
3. Then measures are removed from the end until the file starts opening.
4. Then I find the problematic measure and look at its contents and look for anything that seems suspicious to me.
In reply to Despite what @ILPEPITO says,… by mercuree
I was just guessing, assuming something similar had happened to you before. The strategy you suggest is certainly very valid, even if it seems to require a type of patience that I do not possess. In any case, my sincere compliments. The question remains why it happens so often that files become corrupted.