Time signature crash
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4370, revision: 29165bb
Steps to reproduce:
1. Download the provided sheet (Time_signature_plus_tie_crash.mscz)
2. Add 3/4 signature to first measure
3. Add 4/4 signature to second measure -> crashes
Workaround:
* Remove the generated tie after step 2.
Interestingly, it only crashes if the tie was generated by MuseScore. Removing the tie and re-adding it before doing step 3 prevents the crash somehow.
Comments
Great job working out the steps to reproduce this crash! Possibly related to #279570: Crash when removing added time signature if subsequent tie and rest in next measure
Might be also related to #279593: Crash on changing time signature.
See https://github.com/musescore/MuseScore/pull/4423.
Fixed in branch master, commit 7c8552620e
fix #279761: add a missing list emptiness check
Fixed in branch master, commit 06f181f43f
Merge pull request #4423 from dmitrio95/timesig-crashes
fix #279761, fix #279593: fix crashes on changing time signature
Automatically closed -- issue fixed for 2 weeks with no activity.