Undoing a clef change in first measure results in crash

• Feb 28, 2019 - 20:37
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

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

1) Default score
2) Drag and drop, or double-click, bass clef in first measure
3) Undo

----> crash

Comments

• Feb 28, 2019 - 20:46

A curious thing : I get this crash with the 3.0.4, but not - the clef change appears in first measure/system too - with former or recent nightlies, the last one e.g.: revision: 42af412
Different branch?

Reply

• Feb 28, 2019 - 21:56
Priority ⇒ P0 - Critical

I get the crash if I add to the measure (which indeed doesn't work, a known bug already fixed in master and with a PR pending for 3.0.x). No crash if I add the new clef to the existing clef. And no crash on any recent build from master, presumably because of the fix for the more fundamental bug where the clef doesn't even appear in the first place. So my guess is this will fix itself if/when the PR for [#285020] gets merged for 3.0.x. but let's leave this open to be sure.

Reply