MuseScore 3 loops when loading MuseScore 2 score via double-click
Reported version
3.0
Type
Performance
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Trying to load this music score freezes MS 3.0.5 - every time. Loading it into MS2, doing minimal changes and store back doesn't help.
Attachment | Size |
---|---|
Vi skal ikkje sova burt c.mscz | 37.51 KB |
Comments
Confirmed. Actually it is a score last saved with MuseScore 2.0.2 and created on Linux.
And it hangs in MuseScore 3.1 too.
Turning everything black in that score, using MuseScore 2.3.2, and it loads in MuseScore 3.1
Actually it is sufficient to turn the chord symbols black
and it doesn't freeze or hang, but goes into a loop, monopolizing one CPU/core
Strangly it does not happen in the latest code from master, self-built in QtCreator on Windows
This file opens just fine here with version 3.1
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.7078, revision: e26f7c4
nor does it happen in the latest development build (OS: Windows 7 SP 1 (6.1), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.7087, revision: 5c882aa), so I guess we can consider it fixed for 3.1.1
Even stranger: I can't reproduce it anymore, not in 3.1?
I forgot to mention that I'm not using Windows, but Linux (Mint 18.3). And changing scores color to black did not help. MS 3.1 loops when displaying the dialog box "Reset the positions of all elements?" The dialog box has only a header, no content.
It did loop for me in 3.1 on Windoes 7, but only twice, Once with the unaltered score and another time when only changing the 1st chord symbols' color to black. Not anymore since (and not in between with anything or just all chord symbols set to black), not even with the unaltered score anymore.
A true Heisenbug?
I can't find the 3.1.1 version. Maybe not ready for Linux yet? Anyway, if I start MS3.1 first and then load the file, it succeeds until I try to edit anything. Then it freezes (loops).
I should also mention that other MS2 files seem to work fine, even with colored score symbols (I want them to stand out).
There are numerous other issues as well, but they don't belong here ... :)
MuseScore 3.1.1 doesn't exist yet.
I can confirm the to loop on startup, but not after.
What edit causes it to loop for you?
When I used MuseScore 2 to change the score font from MuseJazz to FreeSerif, the problem disappeared. As most of the MS2 files load fine with MS3, this may have been a coincidence, probably in connection with other factors, but the color doesn't seem to have anything to do with it. So the work-around is: Do not use the MuseJazz until AFTER you have changed to MS3. However, MuseJazz in MS3 doesn't look very nice, so I prefer FreeSerif. :)