Loading a "damaged" score

• Oct 3, 2019 - 17:15
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Start Musescore
Load score
immediate crash

This score was created and saved in this copy of Musescore
A way of loading the score that offers errors (as I have seen before when loading scores from elsewhere) would help then I could fix the problem

Attachment Size
.1st_Symphony.mscz, 33.54 KB

Comments

• Oct 4, 2019 - 07:40
Status needs info ⇒ active

Confirmed, it crashes MuseScore
The latest development build (and most probably 3.3 RC too) loads the score, but crashes as soon as you select the the part tab, also when trying to delete that part

Reply

• Oct 4, 2019 - 07:55

In debugger it crashes right on loading the score. Stack trace:
1 ZN7QPixmapaSERKS_ 0x61bfe097
2 ?? 0x3c3f5bb0
3 Ms::Timeline::barline_meta timeline.cpp 1261 0x528cbd
4 Ms::Timeline::drawGrid timeline.cpp 984 0x527393
5 Ms::Timeline::setScore timeline.cpp 2261 0x52f1ad
6 Ms::MuseScore::setCurrentScoreView musescore.cpp 2665 0x4ea731
7 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 867 0x40d1c1
8 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68c82545
9 Ms::ScoreTab::currentScoreViewChanged moc_scoretab.cpp 211 0x4144cd
10 Ms::ScoreTab::setCurrent scoretab.cpp 252 0x5a6e37
11 Ms::ScoreTab::setCurrentIndex scoretab.cpp 387 0x5a78b2
12 Ms::MuseScore::setCurrentView musescore.cpp 2534 0x4e9e38
13 Ms::MuseScore::setCurrentScoreView musescore.cpp 2517 0x4e9d55
14 Ms::MuseScore::dropEvent musescore.cpp 2836 0x4eafae
15 ZN7QWidget5eventEP6QEvent 0x27c0696e
16 ?? 0x439
17 ?? 0x28c6f8
18 ?? 0x34cc3018
19 ?? 0x2f4dc4d0

Something about an "end-start repeat"

Reply

• Oct 4, 2019 - 07:59

I fixed your score for you. There was an End-start repeat barline in measure 9 of the Menuetto that was triggering an error caused by these 3 lines of code, since there is no corresponding pixmap in the barlines map, which means that we are trying to dereference NULL here. After deleting those 3 lines, I was able to open your score. I deleted the End-start repeat barline, added it back, and saved the file. This one opens without problems in the MuseScore 3.3 Release Candidate.

Attachment Size
1st_Symphony.mscz 45.29 KB

Reply

• Oct 4, 2019 - 08:00

different stack trace next time:
1 ZN7QPixmapaSERKS_ 0x61bfe097
2 ?? 0x41275748
3 Ms::Timeline::key_meta timeline.cpp 1205 0x528888
4 Ms::Timeline::drawGrid timeline.cpp 984 0x527393
5 Ms::Timeline::setScore timeline.cpp 2261 0x52f1ad
6 Ms::MuseScore::setCurrentScoreView musescore.cpp 2665 0x4ea731
7 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 867 0x40d1c1
8 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68c82545
9 Ms::ScoreTab::currentScoreViewChanged moc_scoretab.cpp 211 0x4144cd
10 Ms::ScoreTab::setExcerpt scoretab.cpp 336 0x5a74df
11 Ms::ScoreTab::qt_static_metacall moc_scoretab.cpp 116 0x414169
12 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68c82545
13 ZN7QTabBar15setCurrentIndexEi 0x27b1a1e2

Reply

• Oct 4, 2019 - 10:56

Hmm, I can't reproduce the issue from scratch. So som,ething special must have been going on whith this score, and that might be the explanation why it hadn't been noticed since 3.1 Beta 2, 6 months.

Reply

Fix version
3.3.0