MuseScore 2.0.2 crash

• Aug 14, 2015 - 09:47

Opening this score with MuseScore 2.0.2 (699a5ee) causes MuseScore to crash. (The latest nightly build c2b3bb9 also crashed).

The last time I worked on the score was April 10th. I'm almost certain it was using the vanilla 2.0 version.
I'm running on an iMac however it also crashed on a Windows 7 (64bit) with MuseScore 2.0.2.

The MuseScore Songbook also crashes.

Attachment Size
10_Epilog.mscz 35.99 KB

Comments

And here's the stack trace:

0 Ms::Beam::beamDist beam.h 146 0xbd1f34
1 Ms::Tremolo::layout tremolo.cpp 317 0x8cf742
2 Ms::Chord::layoutStem chord.cpp 1501 0x821981
3 Ms::Score::doLayout layout.cpp 1515 0x80f3e7
4 Ms::Score::update cmd.cpp 175 0x7980f2
5 Ms::readScore file.cpp 2124 0x58ff8d
6 Ms::MuseScore::readScore file.cpp 328 0x581226
7 Ms::MuseScore::openScore file.cpp 309 0x5810f1
8 Ms::MuseScore::loadFiles file.cpp 290 0x580e92
9 Ms::MuseScore::cmd musescore.cpp 4059 0x494991
10 Ms::MuseScore::cmd musescore.cpp 3952 0x494206
11 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 814 0x6a9fdd
12 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68a655a2
13 ZN12QActionGroup7hoveredEP7QAction 0x61dc4b95
14 ?? 0x1e742f40
15 ZN7QAction8activateENS_11ActionEventE 0x61dc3b6e
16 ?? 0x28ca18
17 ?? 0x909001b9
18 ?? 0xf9b425ff
19 ?? 0x909001b8
...

Somehow looks familiar...

Ah, found it: #70416: crash when having a two-notes tremolo between two 16th notes (or lower value) when their beams are set to none , looks like the same problem as described in https://musescore.org/en/node/70381

Do you still have an unanswered question? Please log in first to post your question.