Multiple grace notes cause crash when creating, or opening part
GIT commit: a3d5580
Sorry, it's on the big side, and I have no useful information on what the trigger might be, but am hoping someone with a debug build might be able to sort it out more quickly than I.
FWIW, while we have been in the habit of marking all crashes critical, if there is any room for further prioritization, I would observe that this is a score that I would be interested in using further in 2.0 to test features and so forth. If we could get it working, that would be wonderful.
| Attachment | Size |
|---|---|
| Rhapsody in Blue - nightly.mscz | 73.95 KB |
Comments
I forgot - WIndows 7.
Here is the relevant bit of the backtrace for the crash which also occurs on Ubuntu with build d5f451c...
(gdb) bt
#0 0x00007ffff18d1445 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00007ffff18d4bab in __GI_abort () at abort.c:91
#2 0x00000000008f7b93 in Segment::add (this=0x7ffe4a0, el=0x7ffedc0) at /home/steve/Desktop/SOFTWARE_MuseScore/MuseScore/libmscore/segment.cpp:494
#3 0x0000000000881502 in cloneStaves (oscore=0x54d7a90, score=0x7feb270, map=...) at /home/steve/Desktop/SOFTWARE_MuseScore/MuseScore/libmscore/excerpt.cpp:377
#4 0x000000000088302b in createExcerpt (parts=...) at /home/steve/Desktop/SOFTWARE_MuseScore/MuseScore/libmscore/excerpt.cpp:130
#5 0x000000000099340a in Score::read114 (this=0x54d7a90, de=...) at /home/steve/Desktop/SOFTWARE_MuseScore/MuseScore/libmscore/read114.cpp:378
#6 0x0000000000968801 in Score::read1 (this=0x54d7a90, de=...) at /home/steve/Desktop/SOFTWARE_MuseScore/MuseScore/libmscore/scorefile.cpp:781
#7 0x000000000096a123 in Score::loadCompressedMsc (this=0x54d7a90, name=...) at /home/steve/Desktop/SOFTWARE_MuseScore/MuseScore/libmscore/scorefile.cpp:626
#8 0x00000000007c7cb1 in MuseScore::readScore (this=, score=0x54d7a90, name=...) at /home/steve/Desktop/SOFTWARE_MuseScore/MuseScore/mscore/file.cpp:1736
The trigger is most probably the double grace note on the third beat of the second measure, first part and the fact that you have created the parts in 1.2. Deleting the parts in 1.2 should probably solve the crash on open. But you will not be able to create the parts in MuseScore 2.0 because of #12953: Multiple grace notes not carried in part.
If it's solved by removing the parts, can this bug marked as duplicate of #12953: Multiple grace notes not carried in part ?
Wow, that's it! I was feeling bad because almost none of my 1.2 scores would open in nightly builds, but now that I know that's just because they have parts defined, I am able to remove the parts in 1.2, re-save, and open this one. So presumably that will be the same for others.
And yes, trying to create parts in 2.0 doesn't go so well - either nothing happens or it crashes.
Although it's the same steps, this is a different report: #12953: Multiple grace notes not carried in part
I re-open this one :).
I'm much less concerned with anything having to do with grace motes than the actual crash that occured on opening the score - the fact that merely having parts defined apparently causes crashes in 2.0. But that too may well be a duplicate - perhaps of #15263: Opening attached 1.1 score with parts causes crash?
Just incase: Currently, the linked issue in #6 has the wrong title (a bug?) - it should say 'Multiple grace notes not carried in part', not '[Trunk] Multiple grace notes cause crash when extracting part'.
fixed in 3340d3db35
Automatically closed -- issue fixed for 2 weeks with no activity.