Specific score Causing Musescore to Crash When Running
Reported version
3.4
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
- I download my score "The Canticle of the Doctor".
- I open it in Musescore.
- Try to do anything with the score, it crashes.
| Attachment | Size |
|---|---|
| The_Canticle_of_The_Doctor.mscz | 14.1 KB |
Comments
Same score as here: https://musescore.org/en/node/300317#comment-975003
Tried several things (create parts, change pitch, transpose etc.) Works as expected.
Please describe very exactly what steps you are doing to get a crash.
In reply to Same score as here: https:/… by cadiz1
I did, lol. If I try to do anything with that score after loading it, it crashes. If I try to go to the first note, it'll freeze and crash. If I try to play, it'll crash. It's as simple as I put it, lol.
In reply to Same score as here: https:/… by cadiz1
I have a video of it, if you'd like, but for some reason it won't load here.
Nevermind, just made it into a gif to show what I do.
Here we go.
Ok, when launching playback, I get too.
Ok, so duplicate of #289643: Crash when launching playback in presence of unexpected voltas
Ie: remove the "weird" volta measure 34 in your score, and the problem will be solved.
See: 1The_Canticle_of_The_Doctor.mscz
Volta?
In reply to Volta? by Devyn_Horne
Nvmd, figured it out, lol.
Hey guys, I got the same problem concerning my transcription of Ticheli's Symphony No. 2, where in measures between 25-70 cause the entire program to crash but if I skip to like the middle part of the first movement, it works just fine. Same as with Ticheli's Saxophone and Clarinet concerto, despite while I was working on them, they work just fine. And when I try to upload the symphony here, it still says 'it cannot handle .mscz file' and I tried the File-Save Online but still no use.
Can anyone please help me on these problems?
Please note that this issue is marked as a duplicate and with this essentially closed.
It seems to be a different issue too (and I can reproduce), so please open a new one.
Trying to save online indeed results in:
The score cannot be uploaded, as we don't support this version of mscz files yet.
Sorry for the inconvenience.
But this seems a wrong error message.
Opening it in a debug build I see:
Debug: read future version (...\libmscore\scorefile.cpp:906, void Ms::MasterScore::parseVersion(const QString&))
Debug: no sys staff (...\libmscore\system.cpp:1310, int Ms::System::lastVisibleSysStaff() const)
Warning: unmapped drum note 81 (...\libmscore\chord.cpp:1698, void Ms::updatePercussionNotes(Ms::Chord*, const Ms::Drumset*))
The latter warning repeated numerous times with varying numbers.
Plaining it end with a failed assertion deep inside Qt:
Fatal: ASSERT failure in QList::operator[]: "index out of range", file C:/Qt/5.12.7/mingw73_32/include/QtCore/qlist.h, line 552 (C:/Qt/5.12.7/mingw73_32/include/QtCore/qlist.h:552, )
(Yes, my debug build uses Qt 5.12.7, not 5.9.8 like the released version)
BTW: MuseScore 3.2.3 crashes too on that score, so it isn't a recent regression
For some reason, the culprit is the Change instrument ("mute out") in C trumpet staff, end measure 51.
![mute.jpg]( "mute.jpg")
Remove (or replace it) and from what I see now, the problem is solved.
@Dnetter16: Please in the future, post first in the forum support, since as said, voltas in old scores are unrelated with this/your current issue
in this case an instrument change is not the way to stop the mute part, but another channel switch text, like the 'open' from the text palette. You've used it correctly in other places.
Fixed score attached (it also does "Save online" properly now)