Crash on opening Musescore 2.x file that uses leading space setting on the initial clef
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
See https://musescore.org/en/node/297310 and the score there along with the stack trace and proposed fix...
Workaround is to reset that leading space in 2.x prior to importing the score in 3.x
See https://github.com/musescore/MuseScore/pull/5481
See also #297328: Importing a 2.x score makes initial clefs lose their customized properties for a related issue
Fix version
3.3.4
Comments
Related to #297339: Clef beside header clef saved in 2.x becomes header clef when imported to 3.x, not the same cause.
Fixed in branch master, commit d9abdeb0ea
_fix #297326: Crash on opening Musescore 2.x file that uses leading space setting on the initial clef
which seems to not belong to any segment, so dereferences a NULL pointer
leading to a segment violation (pun intended).
The fix simply ignores this, and this avoids the crash, but also looses
the 'visible' property of that clef for some yet unknown but unrelated reason._
Fixed in branch master, commit 3d9c900d32
_Merge pull request #5481 from Jojo-Schmitz/segment-violation
fix #297326: Crash on opening Musescore 2.x file that uses leading space setting on the initial clef_
Automatically closed -- issue fixed for 2 weeks with no activity.