Crash on opening this score

• Dec 16, 2018 - 20:59
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

Open attached score. Result: segfault.

Ubuntu 18.04, latest master.

Attachment Size
2. Concert Piece v2.mscz 112.33 KB

Comments

Just a note that this is a debug build. Caused by /usr/MuseScore/libmscore/element.cpp:625 - a QFatal because a score element is somehow linked to another score element that isn't the same type.

Priority P1 - High

Are you continuing to investigate? Do you think is bad in the score already, or is it something generated on load? I'd expect the former, in which case, the real question is how did the score get into that state.