Insert measures in mmrest mode leads to corruption/crash

• Sep 5, 2019 - 21:45
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
fixed
Regression
Yes
Workaround
No
Project

Hello,

  • Create a score with 3 measure with 2/4 time signature
  • Add double bar at end of measure 1 and 2
  • Go to mmrest mode with key "m"
  • select measure 2 and Insert 5 (or more) measure with Ctrl-ins (mmrest of 6)
  • Select measure 3 and insert 5 (or more) measure with Ctrl-ins (mmrest of 6)
  • Exit from mmrest mode with key m, you have now 13 measure
  • First measure after second double bar is 4/4

Thanks

Robert

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.2.3.7635, revision: d2d863f


Comments

Title wrong time signature measure when Insert measures in mmrest mode Insert measures in mmrest mode leads to corruption/crash
Regression No Yes
Severity S3 - Major S2 - Critical

Confirmed. And this can lead to very bad things in a score with parts.

Other "minimal" scenario:

1) Load this test file: mm insert.mscz
2) Press "M"
3) Select the mmrest and Insert a measure 
4) Enter a half dotted note in the same mmrest

Unexpected result: four beats, as if the "updating" of the time signature 3/4 had not been done? In any case, it’s really the trigger of this issue

ex1.jpg

5) For the demonstration, complete now the "corrupted" measure with a quarter note -> Create parts -> Save/Reload and Ignore the warning.

You are here: mm insert1.mscz

6) Select the measure and Remove the content (Del). I show this step, because I have already seen similar things in scores on the forums in recent weeks/months with corruptions (type 0/1) in the parts, among others.

So, you get:
ex2.jpg

7) Remove (Del) the G quarter note -> Press Shift + Ctrl + Del (to get a full measure rest)

8) Toggle in part -> Press "M"

Result: corruption type 0/1
Here: mm insert2.mscz

Note: you can get this result in main score if applying steps #6 and #7 in the part.
So: mm insert2 bis.mscz
Of course, it's very easy to get crashes with such scores.

Fix version
3.3.0