Adding measures can crash musescore
If I try to add one or more measures at the end of the score to the attached piece, that crashes musescore.
GIT commit: a254f68
| Attachment | Size |
|---|---|
| What_poor_Astronomers.mscz | 18.94 KB |
If I try to add one or more measures at the end of the score to the attached piece, that crashes musescore.
GIT commit: a254f68
| Attachment | Size |
|---|---|
| What_poor_Astronomers.mscz | 18.94 KB |
Comments
Using e523aad.
1. Appending instantly crashes musescore with that score.
2. After deleting the page break and section break, only adding (appending) 1 measure seems to work. (the second would cause a crash)
Also, inserting many measures crashes musescore (try with the last measure) with this score.
Probably the problem is related to the feature of hiding empty staves: https://musescore.org/en/node/106931
It seems as if it is possible to add measures without a crash after unchecking this feature.
You mean related to #106931: File crashes the program? (Using this syntax makes sure issues get cross-linked)
Famous last words:
Fatal: ASSERT: "!visibleStaves.empty()" in file ...\MuseScore\libmscore\system.cpp, line 379 (:0, )
Stack trace up to this:
1 Ms::mscoreMessageHandler musescore.cpp 2318 0x48b18a
2 Z14qFloatDistancedd 0x6888d42a
3 ?? 0x3
4 ?? 0x28aed8
5 QList::size qlist.h 160 0xc37977
6 Ms::Score::createRehearsalMarkText score.cpp 3700 0x746c75
In the terminal I only had a short line, where also empty + Staves were shown (don't ask me for the correct words, I installed the compiling of musescore on my other computer). Where do I find there the saved "Speicherabzug"?
So, as you say, this might be really a duplicate to #106931: File crashes the program (this line is for testing purpose only, the syntax is not shown in you message, but I found it below ...).
Yes, that's the syntax... sorry I didn't know how to put that in without it being interpreted riught away.
I got the stack trace from running a self-build MuseScore from latest git master in Qt-Creator, on Windows.
No problem ;-). I also used a self-build MuseScore, but started it in the terminal. Unfortunately it doesn't give much information ..., beside "Speicher-Zugriffs-Fehler" and that the "Speicher-Abzug" is written.
Better run it in Qt-Creator, and there in Debugger (you can attach the debugger to a running process there)
To catch the "Fatal", set a breakpoint at ...score/musescore.cpp, line 2317
I will try to do that this evening.
Fixed in branch master, commit d789e2e691
fix #107001: Adding measures can crash musescore
Automatically closed -- issue fixed for 2 weeks with no activity.