This score causes ram to spike and force my computer into blue screen
I've been opening this file for more than a few months but suddenly it cannot be opened anymore, not sure if it was corrupted or anything.
I would appreciate if anyone could help me fix this file.
Attachment | Size |
---|---|
Large Ensemble.mscz | 30.7 KB |
Comments
I can confirm the issue with MuseScore 3.6.2 (no blue screen though, but indeed eating all memory)
With 3.5.2 (in the case the PortableApp version) though the score opens just fine
In reply to I can confirm the issue with… by Jojo-Schmitz
So should I revert my musescore version to continue working on this score? Or is there a way to fix this file?
In reply to So should I revert my… by ckhansel21
You could use the 3.5.2 PortableApp, just for this score, and the installed 3.6.2 for all others?
At least until you found out what's causing the issue
Culprit found: the staff type changes in the 2nd part, Oboe, in measures 55 and 62, deleted in 3.5.2 and saved the score, that then opens in 3.6.2
In reply to Culprit found: the staff… by Jojo-Schmitz
That is amazing, really appreciated it. Keep up the great work, and have a nice day.
Thank you for everything!
In reply to That is amazing, really… by ckhansel21
There's still a bug lurking, and even the latest development builds are affceced, so it'd be good to report this in the issue tracker, as a Critical 3.6 Regression
In reply to That is amazing, really… by ckhansel21
Thanks for #332265: This score causes ram to spike and freezes my computer