MSCZ backup file crashes Musescore 2.0.3

• Aug 30, 2016 - 06:07

Hello fellow Musescorians,

I was working on a piece for Harp for a friend. I had only worked on it for about an hour before I attempted to adjust the stretch of the score. However, I noticed the "stretching" wasn't being applied, and shortly afterwards the entire program crashed.

I looked for the backup file and found it, however anytime I open it says that a "Previous session closed unexpectedly" and asks if I want to recover it, and whether I click YES or NO, musescore crashes and poof. Done.

It's infuriating because a second time I tried re-writing this piece (I "snapchatted" a portion of it to my friend and was able to get a screengrab) and tried re-writing it. This time I saved an actual copy and was saving frequently. I closed out after a certain point and found that not only had the back-up file not saved any of the recent changes on it, but me MANUALLY SAVING IT had no effect either.

So now the original I was working on crashes Musescore, and the newer one that I tried re-writing didn't even save properly. What is going on??

I was reading elsewhere here on the forums about using glissando in some spots that can cause the file to crash...I know nothing of the "technicalities" behind Musescore and am just wanting to know if there's any way I can recover the old file at this point.

Attaching the autosave backup of the first session.
EDIT: I am also using Windows Vista. Outdated, I know, hope this has nothing to do with the functionality of the program.

Attachment Size
scZr8752.mscz 25.22 KB


Obviously, this score is corrupted and crash at the opening, indeed.

Is it a score you created initially with MuseScore? If so, which version (2.03, 2.0.2, other), and by specifying the steps which could lead to this kind of problem.
Or is it an imported file (MIDI, Pdf conversion , MusicXML, others) that you have re-worked thereafter with MuseScore?
In these later cases, it would helpful to attach the score in its "original" format (and in the same way, by describing what you have specifically done after that)

In reply to by cadiz1

It apparently got created (or last saved) with 2.0.2) on Windows (Vista, as the OP confirmed), no traces of any Import.
The latest build from master chrashes on it too

Problem is a glissando that is in the file twice. Fixed file attached. It still has quite a lot glissandos, at places where I woudn't really expect them

Attachment Size
scZr8752.mscx 50.56 KB

In reply to by Jojo-Schmitz

Stack trace:
1 QVector::append qvector.h 629 0xd8acb9
2 QVector::push_back qvector.h 252 0xd8afb5
3 Ms::Note::addSpannerBack note.h 413 0xceb772
4 Ms::Note::read note.cpp 1082 0x7d8bc6
5 Ms::Chord::read chord.cpp 956 0x81bd35
6 Ms::Measure::read measure.cpp 1641 0x7b45e4
7 Ms::Score::readStaff scorefile.cpp 271 0x7fda78
8 Ms::Score::read scorefile.cpp 955 0x8022e3
9 Ms::MasterScore::read1 scorefile.cpp 917 0x801ff3
10 Ms::MasterScore::loadCompressedMsc scorefile.cpp 769 0x801074
11 Ms::MasterScore::loadMsc scorefile.cpp 816 0x801510
12 Ms::readScore file.cpp 2034 0x5a35d6
13 Ms::MuseScore::readScore file.cpp 328 0x5944c2
14 Ms::MuseScore::openScore file.cpp 309 0x59438e
15 Ms::MuseScore::loadFiles file.cpp 290 0x594050
16 Ms::MuseScore::cmd musescore.cpp 4609 0x49d690
17 Ms::MuseScore::cmd musescore.cpp 4479 0x49cd94
18 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 824 0x696944
19 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68a08842
20 ZN12QActionGroup7hoveredEP7QAction 0x1b3a5295

It indeed crashes whelile working on a glissando

So crashes anywhere between 2.0.2 (f51dc11, Jul 16 2015) probably even earlier, and 7383524 from yesterday

(and no, Vista has nothing to do with it, it crashes here on Windows 7 too)

In reply to by Dylan Monacelli

Glissandos normally work fine; I've never heard of another report of a similar problem. You just aparently hit on some really unusual sequence of operations no one else has ever tried and that is what triggered the bug.

Until you or someone else figures out how to reproduce the bug from scratch, it's unlikely it can be fixed, but also, since no one else has reported similar problems, it's also pretty unlikely you'd ever hit on that exact sequences of problematic steps by accident again. Just use glissandi normally, if you ever see a problem again, try to remember what you did and report it, but chances are that won't be an issue.

Do you still have an unanswered question? Please log in first to post your question.