Save selection which starts with a multimeasure rest leads to crash

• Feb 10, 2018 - 12:17
Reported version
2.1
Priority
P0 - Critical
Type
Functional
Frequency
Few
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Version 2.1 (same behaviour with 2.2 dev. and 3.0 dev.) / Windows10

1) Load this file: test0.mscz
2) Range selection of the mm rest (only), or with the next measure
3) File -> Save selection
4) Save/Close/Reload
Result: crash: test mmrest.mscz

Works as expected if the selection includes a plain measure before the multimeasure rest: test1.mscz

Comments

• Nov 13, 2018 - 17:40
Severity S3 - Major ⇒ S1 - Blocker
Frequency ⇒ Few
Priority ⇒ P3 - Low
Regression ⇒ No
Reproducibility ⇒ Always
Workaround ⇒ No

Reply

• Nov 16, 2018 - 18:31
Status PR created ⇒ fixed

Fixed in branch master, commit d4b80d0968

fix #269309: handle MMRest properly on "Save selection" operation

Currently any range being written must start with a usual measure,
if that measure has MM rest it will trigger its writing. This patch
assures this assumption for selection writing.

Reply