Musescore.exe has stopped working, and it's triggered by this one score.

• Feb 14, 2017 - 03:43

Greetings,

I started using this program at the beginning of the year, and have been pleased with its performance so far. That is until today, when I went to open a score I'd been working on imputing into the program. I was working for a few minutes when, all of a sudden, it gave me the "musescore.exe has stopped working" thing. So, I pulled it back up and tried again and got the same problem after a few minutes, then I rebooted and reinstalled to no avail. It seems I can work on it for a bit then when I try to save the file again it results in the "musescore.exe has stopped working" crash. After doing some research, I think it has something to do with the glissando I put in yesterday in the harp part, because some of the other reports I have read have had similar problems with glissandi, but I have no idea how to fix it. I've attached the finicky score below. Please help if you can.

As far as I can tell this can be recreated by:
1. opening the score
2. inputting a 2/2 time signature on the end
3. then attempting to save

Thanks

Attachment Size
City_Trees.mscz 21.78 KB

Comments

• Feb 14, 2017 - 08:15

The problem is in Ride Cymbal measures 24/25 involving the glissando extending on 2 measures.
By deleting the quarter note measure 25 or the glissando measure 24, and by adding eg a 2/2 time signature in measure 25: no issue.
I think I can reproduce from scratch (Continuous View is involved too in my understanding presently). And, interesting, I can get after the crash a file with 0 octets.

Reply

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