Musescore crashed playing score

• Dec 15, 2020 - 15:57

Musescore timidly crashes when playing the attached score.

Faulting application name: MuseScore3.exe, version:, time stamp: 0x5f8a11a3
Faulting module name: MuseScore3.exe, version:, time stamp: 0x5f8a11a3
Exception code: 0xc0000005
Fault offset: 0x00000000007e0feb
Faulting process id: 0x321c
Faulting application start time: 0x01d6d2f43deab186
Faulting application path: C:\Program Files\MuseScore 3\bin\MuseScore3.exe
Faulting module path: C:\Program Files\MuseScore 3\bin\MuseScore3.exe
Report Id: bb5df890-eb98-4448-912c-5ccb6553475f
Faulting package full name:
Faulting package-relative application ID:

Attachment Size
Report_wer.txt 34.03 KB
DanceInAm2.mscz 4.53 KB


It's a 1.3 score and I can confirm it crashing 3.5.2 if you hit the rewind button after importing it.
However if you then save the score, close it and reopen it, it plays back just fine.

Confirmend even in the latest 3.x development build, stack trace:
1 QMap::isEmpty qmap.h 362 0x103bc0c
2 QMap::empty qmap.h 597 0x103b9e5
3 Ms::Staff::channel staff.cpp 931 0xa8db9c
4 Ms::MidiRenderer::renderSpanners rendermidi.cpp 1075 0xa32c2b
5 Ms::MidiRenderer::renderChunk rendermidi.cpp 2378 0xa382ac
6 Ms::Seq::renderChunk seq.cpp 1049 0x473e9d
7 Ms::Seq::collectEvents seq.cpp 1095 0x474113
8 Ms::Seq::canStart seq.cpp 332 0x4706f9
9 Ms::ScoreView::::operator()(Ms::ScoreView *, const QByteArray &) const scoreview.cpp 2169 0x636d11
10 std::_Function_handler>::_M_invoke(const std::_Any_data &, Ms::ScoreView *&&, const QByteArray &) std_function.h 316 0x6521ec
11 std::function::operator()(Ms::ScoreView *, QByteArray const&) const std_function.h 706 0x109658d
12 Ms::ScoreView::cmd scoreview.cpp 2879 0x63e894
13 Ms::ScoreView::cmd scoreview.cpp 2081 0x636839
14 Ms::MuseScore::cmd musescore.cpp 6636 0x432e1e
15 Ms::MuseScore::cmd musescore.cpp 6063 0x42f721
16 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 523 0x5e2b88
17 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947f8
18 Ms::ScoreTab::actionTriggered moc_scoretab.cpp 225 0x601ad6
19 Ms::ScoreTab::qt_static_metacall moc_scoretab.cpp 110 0x60155e
20 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947f8

The crash appears to be due to a bad slur (track and tick both set to -1, length of 0 ticks). As far as I can tell the issue happens around measure 20 or so, you can see it is you click all the slurs in the object debugger. Since saving the score appears to fix the problem - these bogus slurs don't get saved apparently - it's probably not worth worrying too much about. But certainly we could detect these bad slurs in renderSpanners to avoid this crash. Most likely it would crash eventually anyhow though. So better to figure out how they got there - bad info in the file itself I guess, but we could presumably detect it better.

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