segfault on score load

• Apr 15, 2018 - 23:35
Reported version
2.1
Type
Functional
Severity
S2 - Critical
Status
won't fix
Project
MuseScore
Tags
2.3
opencrash

Load attached score, get:
a lot of
Score::removeSpanner: Slur (0x555558e54dc0) not found
and a few
Score::removeSpanner: TextLine (0x555558e43880) not found

followed by

Thread 1 "musescore" received signal SIGSEGV, Segmentation fault.
0x0000555555e84fce in Ms::SLine::layout() ()
(gdb) bt

0 0x0000555555e84fce in Ms::SLine::layout() ()

1 0x0000555555e8760e in Ms::LyricsLine::layout() ()

2 0x0000555555e7fb93 in Ms::Score::doLayout() ()

3 0x0000555555f7dd3e in Ms::Score::update() ()

4 0x0000555555b6445b in Ms::readScore(Ms::Score*, QString, bool) ()

5 0x0000555555b6498a in Ms::MuseScore::readScore(QString const&) ()

6 0x00005555559df811 in ?? ()

7 0x0000555555895dca in main ()

=========================
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 2.2.1, revision: 51b8386

The same also happens with MuseScore-2.2.1-x86_64.AppImage

Comments

• Apr 16, 2018 - 08:24
Severity S3 - Major ⇒ S2 - Critical

2.1 on Windows (Portable App) crashes too, as a322ad3 (master branch). Stack tzrace there:
1 Ms::Segment::stretch segment.h 185 0xe06580
2 Ms::Measure::stretchMeasure measure.cpp 3052 0x80214c
3 Ms::Score::collectSystem layout.cpp 3129 0x7e2ebc
4 Ms::LayoutContext::collectPage layout.cpp 3512 0x7e59e3
5 Ms::LayoutContext::layout layout.cpp 3804 0x7e7330
6 Ms::Score::doLayoutRange layout.cpp 3791 0x7e722e
7 Ms::Score::update cmd.cpp 221 0x8c6603
8 Ms::readScore file.cpp 2213 0x5d4e64
9 Ms::MuseScore::readScore file.cpp 329 0x5c3ae6
10 Ms::MuseScore::openScore file.cpp 310 0x5c39c0
11 Ms::MuseScore::loadFiles file.cpp 291 0x5c36a1
12 Ms::MuseScore::cmd musescore.cpp 4888 0x4b1cbc
13 Ms::MuseScore::cmd musescore.cpp 4742 0x4b12cf
14 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 738 0x6e293d
15 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68c7b972
16 ZN12QActionGroup7hoveredEP7QAction 0x20784d75

Reply

• Oct 9, 2018 - 09:49
Status (old) active ⇒ won't fix
Status active ⇒ won't fix

For 3.0 the score is considered corrupted by MuseScore but still loads and does not lead to a crash.
For 2.X I'll mark it "won't fix" as no updates for this branch are planned.

Reply