Select note values onto multimeasure rests in parts leads to corruption and crash

• Jul 27, 2016 - 11:08
Reported version
2.1
Type
Functional
Severity
S2 - Critical
Status
closed
Project

2.0.3 version / Windows 7

First reported: https://musescore.org/en/node/119526

1) "My First Score"
2) File -> Parts -> New All -> Ok
3) View part
4) Select the multimeasure rests (hightlighted)
5) Press 4 (or select the 8th note value)

Result: corruption in part (after press M for disable the mm. rests), and in main score.

main score.jpg

- Other example which leads to a crash:

At step #5: type 8, or select the double whole note instead the eight note value
6) Go in main score: enter five half notes
Result: crash
crash2.jpg


Comments

After checking, it's a very former issue.
I can reproduce with quasi similar results since more than two years, May 2014, with this Nightly:56177c3

The differences?

First, after the step #5, I receive the same result, ie (image below) but only in main score (not in part, correct, after disable the mm rests)
main score.jpg
But, if I return in part, and applies a new note value (eg a 16th), I receive this in part:
flute part (1).jpg
And this in the main score:
flute part (2).jpg

Title Select note values onto a multimeasure rests in parts leads to corruption and crash Select note values onto multimeasure rests in parts leads to corruption and crash

Behaviour confirmed for 2.0.1. (b25f81d). Here is the crash report (after attempting to enter that 5th half-note):

Problem Event Name: APPCRASH
Application Name: MuseScore.exe
Application Version: 0.0.0.0
Application Timestamp: 0d2e4580
Fault Module Name: MuseScore.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 0d2e4580
Exception Code: c0000005
Exception Offset: 0039b851
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789