Score keeps crashing, other scores are working fine
Hey everybody! I'm having a problem with one of my scores. If I make an edit and try to save, or if I have the score open for more than a few minutes, the program crashes. The crash reporter pops up, but doesn't give me any info on what happened. Earlier today, a corruption alert came up for the same score (which I dealt with successfully) but I'm not getting any such notices now. And to further complicate things, other scores seem to be working just fine. I'll post the score in question down below, thanks for the help!
| Attachment | Size |
|---|---|
| Anakin's Dark Deeds.mscz | 44.31 KB |
Comments
Try to eliminate the Parts, save and regenerate them.
In reply to Try to eliminate the Parts,… by Shoichi
I've looked through the score, and it appears fine to me. I can't identify any specific parts that it could have a problem with.
In reply to I've looked through the… by Charlie Latkowski
The original file 'freezes', try this
In reply to The original file 'freezes',… by Shoichi
Thank you so much! Out of curiosity, what did you change? That way I can fix the problem if it pops up in the future.
In reply to Thank you so much! Out of… by Charlie Latkowski
I've eliminated the Parts, saved them and regenerated but I'm using an outdated version
OS: Linux Mint 19.3, Arch.: i386, MuseScore version (32-bit): 3.2.3+dfsg1-4~ppa1804+1
In reply to I've eliminated the Parts,… by Shoichi
To clarify, what does eliminating, saving, and regenerating the parts entail?
In reply to To clarify, what does… by Charlie Latkowski
Some previous forum conversations have shown that, sometimes, making changes to the Parts or to the score, when they have already been created may cause interference. So I just suggested the method that can often solve the problem. I ignore the specific 'why'. Usually it seems safer to generate the Parts at the end.
https://musescore.org/en/handbook/parts#delete
In reply to Some previous forum… by Shoichi
Ok, thanks again for the help!
In reply to Ok, thanks again for the… by Charlie Latkowski
You're welcome.
MuseScore does not report corruption in part, only in the main score. Those you got reported earlier and fixed them probably are still existing in the part(s), and there causing crashes on (auto)save.
Culprit here BTW is the first part (B♭ Trumpet 1), so just deleting that (File > Parts > Delete) and then regenerating it fixes the crash