This score causes ram to spike and freezes my computer
Reported version
3.6
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
Yes
Workaround
Yes
Project
Apparently the staff change type in the Oboe part (measure 55 and 62) and probably, staff type change in measure 66 as well probably caused the file to use alot of the computer memory.
| Attachment | Size |
|---|---|
| Large Ensemble.mscz | 30.7 KB |
Comments
Confirmed, workaround is to remove these staff type changes in a 3.5.2 PortableApp (or any other pre 3.6 version)
And this issue is still the case in current development builds
All 3.6.x PortableApp versions just crash on that score, directly on load.
There is no staff type change in measure 66, and the one in 62 is not the culprit, deleting the one in 52 is sufficent (for the score to load properly in 3.6)