Crash when moving beam if first note of beam is in the first measure and other notes of beam are in the second measure

• Mar 1, 2019 - 02:53
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project

Similar to https://musescore.org/en/node/281154.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.4.5763, revision: cda4080

Step to reproduce:
1. Create one 8th note in the end of the first measure, leaving rest notes in front of it.
2. Create one 8th note in the beginning of the second measure.
3. Set the second 8th note's beam mode to "beam middle".
4. Beam appears. Now double click the beam and try to move it. Then crash happens.
The file bug2.mscz shows this case.

Note that the crash will not happen if more than one note of the beam is in the first measure.
The file not crash.mscz shows this case.

Maybe it looks duplicate of #281154: Crash with first note of measure set to beam middle and nothing to beam to. But in #281154: Crash with first note of measure set to beam middle and nothing to beam to, it's the half note that is in the first measure, and the part of beam attached to that half note, is not shown properly.

Attachment Size
bug2.mscz 6.02 KB
not crash.mscz 5.54 KB

Comments

Fixed in branch master, commit 00ed31b255

_Merge pull request #4743 from songchaow/fix_cross_measure

fix #285100: Crash when moving beam if first note of beam is in the first measure and other notes of beam are in the second measure_

Fixed in branch 3.0.5, commit 2d73b5adb1

_Merge pull request #4743 from songchaow/fix_cross_measure

fix #285100: Crash when moving beam if first note of beam is in the first measure and other notes of beam are in the second measure_