Remove tuplets after inserting measures causes corruption/crash
Reported version
3.1
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
2.2.1 version (also in currents 2.3 dev. and 3.0 dev.) / Windows7
1) Default "Untitled" score
2) Create eg triplets in a measure, no matter which one
3) Select this measure -> Add -> Measure -> Insert one measure
4) Select and remove the triplets
Result: corruption
Intermediate result
Final result:
As expected :
5) click near the "double" barline ---> crash
-
From what I see, all figures of tuplets are impacted
-
And by inserting more than one measure (eg 4 - image below - or more), you get:
-
First noticed in this thread: https://musescore.org/en/node/272169
Fix version
3.6.0
Comments
With a little surprise, I note that this issue was already active with version 2.1.
Further investigation in progress.
Well, more and more surprised that this issue has not yet been reported.
Indeed, after checking, as far back as I go back in time, I note systematically the same problem.
See the screencast below, produced with this nightly (May 2014): e581255
See fix #272172: Remove tuplets after inserting measures causes corruption/crash #3662.
Fixed in branch master, commit 4e14bbcc3c
fix #272172: Remove tuplets after inserting measures causes corruption/crash
fix #272185: Delete a measure containing some tuplets + rest leads to corruption after inserting a measure
Fixed in branch master, commit 344d332429
Merge pull request #3662 from mattmcclinch/272172-remove-tuplets
fix #272172: Remove tuplets after inserting measures causes corruption/crash
Fixed in branch 2.3, commit 3739f11aa5
fix #272172: Remove tuplets after inserting measures causes corruption/crash
manually merged changes, see https://github.com/musescore/MuseScore/pull/3662
Automatically closed -- issue fixed for 2 weeks with no activity.
I am marking this as "active" again, since the original steps once again cause the same errors to occur. Furthermore, this is the same issue described in https://musescore.org/en/node/311919. The cause is clear; the one line from the fix that actually made all the difference was removed some time ago, as pointed out here. All that is needed is to add it back in.
Issue apparently came back with (rather shortly before) 3.1
See https://github.com/musescore/MuseScore/pull/6696.
Fixed in branch 3.x, commit 7294641479
Fix #272172: Remove tuplets after inserting measures causes corruption/crash
Automatically closed -- issue fixed for 2 weeks with no activity.