Crash on opening Musescore 2.x file that uses leading space setting on the initial clef

• Nov 19, 2019 - 09:25
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


Comments

Status PR created fixed

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._

Fix version
3.3.4