MuseScore 3.4.2.9788 Crashing on Playback, OS Windows 10

• Feb 10, 2020 - 21:33

My problem actually started two days ago, Saturday, February 8, 2020.

I was about to playback three scores that I had been working on throughout the previous week and begin working on another. All four scores were open at once (I only mention this to state the condition, because I had as many as maybe 20 open at once before with no problem). Anyway, I began to playback one of the three completed scores and MuseScore 3 crashed. It asked me to send the report and relaunch. When I did it asked me if I wanted to restore last session that stop unexpectedly. I did. All four scores were again opened, and I tried to playback a different score than before. The same thing happened again. I got frustrated, decided to leave it alone and worked on something totally different than MuseScore.

The next day, Sunday, February 9, 2020, my intention was to check for updates to Musescore. However, I could not check for updates from the program. I then tried to come to Musescore.org and could never reach the website. I really thought Musescore was no more. Luckily, this morning I realized that the site was back accessible for me.

This afternoon, February 10, 2020, I again went through the same procedure as Saturday and still got the same result. I decided to update Musescore. I went through that procedure, then tried it out. I still had the same issue/problem. I then decided to uninstall Musescore and since I now had access again to Musescore.org re-install the program directly from the site, Ver. 3.4.2.9788.

After re-installing, I tried something different and opened one of my older and longer scores, which opened and played through fine (over 6 minutes of playback). I closed the older score and then open one of the files that Musescore crashed during playback on Saturday. That song score also playback through completion. I was thinking problem had been solved, but in fact, it just had taken a little longer this time. After closing that score and opening the next score, less than 2 minutes into the 3rd score playback the program again crash.

I'm only listening to playback and not making any changes. God forbid I start creating/editing scores again the program crashes, and I lose all my work. I didn't "restore the previous session that ended unexpectedly", and I opened individual files from their file directory and the program still crashed at the beginning of the score. And, this is not happening on the same score, but on different scores. So in my opinion this is a problem with the program, not the scores.

Can anyone help or has seen such a thing happen before before I start trying to create more scores with Musescore?

Comments

• Feb 10, 2020 - 23:28

Best guess is that the score contains a corruption, perhaps in one of the parts, and is crashing on the auto-save that happens every two minutes. But in order to understand and assist better, we would need you to attach the score you are having problems with. Even though you say it happens on multiple scores, it's likely that whatever actions you took that triggered the bug that caused a corruption in one score, you may well have performed those same actions and thus triggered the same bug with the others.

Reply

• Feb 10, 2020 - 23:55

I'll attach one of the scores. But usually, when this happens I normally get an indication that the score is corrupted and where the corruption is, staff and measure, when I re-open the score. I can go to that staff/measure (s) and correct the issue and then there is no more problems. Since you said that, the score that I'm attaching kept giving me issues with incorrect measure beat counts while I was scoring, i.e. I'd notice that measures had either a 15/16 or 17/16 count when it should have been 4/4, but there was never and indication when I re-opened the file that the score was corrupted. I can't figure out what I could possibly have done to cause this issue but I do recall it happening. I renamed all four files and the other files stopped having the issue. In fact, I was able to edit and save those edits on those scores without incident; but when I opened this file, and didn't even do anything with it, I realized MuseScore crashed again in the background as I was working on something else. The file is attached below if you can do an analysis to determine the issue.

Attachment Size
7a I Learned From The Best.mscz 63.72 KB

Reply

• Feb 11, 2020 - 02:53

@ALawer... Earlier you wrote:
...less than 2 minutes into the 3rd score playback the program again crash.

Is this file you attached, "7a I Learned From The Best", the same one as the 3rd score you mentioned above?

[Also, to any devs here: This does not crash MuseScore 3.34 on Windows 10. (I haven't upgraded yet.)]

Reply

• Feb 11, 2020 - 04:08

While MuseScore will indeed warning you about most corruptions in the score itself, there are some it won't detect, and it won't any that exist only in parts, which is why I mentioned that possibility specifically.

In any case, though, I wasn't able to reproduce a problem either. I tried to trigger it by making a small change to the score then waiting for the autosave to kick in, also then hitting Play and waiting some more, but not crash for me.

Reply

• Feb 12, 2020 - 02:17

Jojo-Schmitz, I found the answer to my question as you gave the details to someone else that previous had a questions concern the term "delete and regenerate":

Addie8585 • Jun 28, 2019 - 21:11In reply to this is the same score as… by Jojo-Schmitz
Right, that's the one. By regenerating, do you mean deleting each instrument and adding them back in?

Reply

Jojo-Schmitz • Jun 28, 2019 - 21:12In reply to Right, that's the one. By… by Addie8585
No, File > Parts

I did not understand what you meant by "corruption in the (only) part" and "delete and regenerate". I actually thought you mean delete the entire score and regenerate the whole thing from scratch. But that could be correct be it appears that you "corrected the problem".

I was able to duplicate the correction on my end.

I still would like to know what caused this and how I can prevent this from happening in the future.

THANK YOU!!!

Reply

• Feb 12, 2020 - 02:36

Nothing you do should ever cause corruption. But there are any number of bugs in the program that can cause it, if you happen to hit upon just the “right” conditions to trigger it. Unfortunately there is no way to know for sure what happened here. If you ever catch it in the act - like you see the corruption happen upon performing some action - do let us know. We try to fix those bugs as soon as they are reported. So it’s entirely possible that whatever caused this is already fixed.

Reply

• Feb 12, 2020 - 05:15

How this can happen has never been fully understood, but there was a code change recently that at least has the potential to prevent this from happening, by making sure I'm a better way that score and part stay in sync. That won't help for scores that have the problem already though.

Reply

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