Certain corrputed (?) files causing MuseScore 2 to take up 100% CPU on OS X
I've discovered that certain files cause MuseScore 2 to take up 100% CPU on my system. The computer heats up and MuseScore becomes sluggish during playback or editing. This has happened twice so far, both times with files that were not unusually large or complex (quintuplets, perhaps?).
The most recent time I realized something was wrong when rests for Voice 2 that I had deleted before had reappeared somehow and some dynamic markings were messed up (an mf and a p had disappeared, an mp appeared in the next bar over from where I had put it, etc.). I was able to recover an earlier version of the file from the .XYZ.mscz, file. The most recent edits I had made were gone, but the anomalies I had observed the first time (Voice 2 rests reappearing, dynamic markings off position) were not there either. MuseScore was also running without consuming 100% CPU.
This leads me to believe something went wrong when the file was being opened and the problem persisted after I had saved and reopened it.
I still have a version of the file, if that's needed.
| Attachment | Size |
|---|---|
| Screen Shot 2016-09-16 at 7.03.06 PM.png | 1.95 MB |
| corrputed.mscz | 62.43 KB |
Comments
Yes, that sample file would be needed in order to reproduce the problem
In reply to Yes, that sample file would by Jojo-Schmitz
I've attached the file now.
In reply to I've attached the file now. by Kaiser W.
What are the steps to reproduce the problem once we load the file you attached? The file *looks* corrupted in that several measures appear to have no notes or rests in them, but I don't think it really is corrupted. I think the notes were just moved to the wrong staff for some reason, using the cross-staff notation facility in situations where it probably rerally should have just used multiple voices. Hard to say for sure.
In reply to What are the steps to by Marc Sabatella
Simply opening the file causes MuseScore to consume CPU like crazy. I don't know if the problem occurs on Windows or on versions of OS X earlier than 10.11.6.
In reply to Simply opening the file by Kaiser W.
I don't see any such problem on Ubuntu. Do you have the Navigator open? In certain cases where MsueScore has a hard time deciding whether or not it can fit all the pages in the screen or not, it can go crazy. Simply turning off the Navigator - or even just resizing it - solves the problem instantly.
In reply to I don't see any such problem by Marc Sabatella
For some reason the problem is not occurring anymore (even before I tried closing the Navigator).
In reply to For some reason the problem by Kaiser W.
FWIW, if it was the Navigator problem, then I could also imagine it going away if the main window itself were resized, or one of the side panels changed, or probably any of a lot of other variables that could cause that particualr "race condition" to go away.