Crash on importing 1.x score with slur without start chord

• May 6, 2015 - 13:53
S2 - Critical

Opening the attached score in 2.0 crashes

Reported in

Stack trace:
0 Ms::Slur::layout slur.cpp 1390 0x825596
1 Ms::Score::doLayout layout.cpp 1547 0x8030eb
2 Ms::Score::update cmd.cpp 175 0x78cb86
3 Ms::readScore file.cpp 2111 0x58a007
4 Ms::MuseScore::readScore file.cpp 322 0x57bbea
5 Ms::MuseScore::openScore file.cpp 303 0x57bab5
6 Ms::MuseScore::loadFiles file.cpp 284 0x57b856
7 Ms::MuseScore::cmd musescore.cpp 3992 0x491dd9
8 Ms::MuseScore::cmd musescore.cpp 3885 0x49164e
9 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 810 0x69ea16
10 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68a64e31
11 ZN12QActionGroup7hoveredEP7QAction 0x61dc4b95
12 ?? 0x1e0880d0
13 ZN7QAction8activateENS_11ActionEventE 0x61dc3b6e
14 ?? 0x28ce08
15 ?? 0x909001bb
16 ?? 0x286825ff

It dereferences m1->ticks(), without checking first whether m1 ain't NULL. Not sure why startCR()->measure() does give a NULL though?

Attachment Size
Divertimento_No17_VI_Rondo-score.mscz 64.2 KB


The start element for the slur is a grace note, but that grace note has a parent of null - suggesting it has not yet been added to a chord. Not sure what triggers this, as a simple test score with a slur from a grace note (created in 1.3) works fine.

The problem seesm to be one or more or the slurs on the slurs grace notes used as trill endings. See for example measure 279. I can't tell what those grace notes are attached to - and apparently, neither can MuseScore 2.0. It looks like some sort of clever trickery was used to create those trill endings in 1.3 (in 2.0, these would be "grace notes after").