Changing "Actual Measure Duration" under a volta causes crash
MuseScore 2.0.1 crashes when the following is performed on the attached file:
* Delete the last 2 notes (2 16th notes under a closed volta) in the last measure.
* Right-click on the last measure. Select "Measure Properties".
* Change the "Measure Duration Actual" to "3/8".
* Click "OK" or "Apply". The application then crashes.
Note: the crash does NOT occur if the volta is removed before changing the actual measure duration.
GIT commit: b25f81d
Attachment | Size |
---|---|
CrashTest.mscz | 6.8 KB |
Comments
No crash here, so there must be something else going on. Which OS are you on? Seems the score got created on Linux
I'm using the Mac version, running under OS X 10.10.3. The specific build of MuseScore is 2.01 Revision b25f81d. For me, the crash happens consistently, not just intermittently.
Intersting, as 1.3 had a similar problem on Yosemite, but 2.0 never had so far.
I can't reproduce either with the psoted score
Can you see if this also happens for you if it is not the last measure of the score? Can you try some other variations - lengthening instead of shortening the measure, for instance - to see if you can narrow it down further?
Shortening a measure with a volta line works fine as long as it is not the last one of the score. Also, lengthening the last measure does not cause a crash. However, it does crash if I first lengthen the last measure and then shorten it to less than its nominal length.
One thing I did notice is that if I shorten a measure with a volta line in the middle of a score, the line gets automatically extended over the following measure (which is probably not the desired behavior). Perhaps when this is done on the last measure, MuseScore tries to extend the volta line to the following non-existent measure, thereby causing the crash. I attached a screenshot showing what happens when I shorten a middle measure that has a volta line.
Thanks for the additional investigation! Although I cannot reproduce the crash, I strongly suspect your analysis will turn out to be correct.
Can anyone reproduce this under a debugger and/or get a stack trace?
It appears likely this is connected to https://musescore.org/en/node/66396 and will have the same root cause & fix.
https://github.com/musescore/MuseScore/pull/2094
It never crashed on my system, but now that we understand the cause, I feel pretty confident that this *should* fix it.
Fixed in branch master, commit 87d40d11e6
fix #63231: crash shortening a spanner
Fixed in branch master, commit e44f841de3
Merge pull request #2094 from MarcSabatella/63231-crash-shortening-spanner
fix #63231: crash shortening a spanner
Fixed in branch 2.0.2, commit ea43dd95f7
fix #63231: crash shortening a spanner
Automatically closed -- issue fixed for 2 weeks with no activity.