Crash when deleting a local Time Signature.
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
To reproduce the crash:
1) Load Local_TimeSig,mscz
2) Create a local 6/4 TimeSig in measure 3 (stave 1, 2 or 3).
3) Select the local 6/4 TimeSig in measure 3 and deleted it.
Expected behavior: A deleted local TimeSig.
Observed behavior: A crash.
Workaround: Create a global 3/4 TimeSig in measure 3 and then delete the TimeSig. Now MuseScore doesn't crash.
Other observation: If instead of a local 6/4 TimeSig a local 3/8 or a local 6/8 TimeSig is used, then MuseScore will not crash. It looks like MuseScore will crash if the local TimeSig hold a larger length as the global TimeSig.
| Attachment | Size |
|---|---|
| Local_TimeSig.mscz | 5.55 KB |
Fix version
3.5.0
Comments
Before deleting the local TimeSig, replace it by a global TimeSig.
@njvdberg Have you worked in a release or debug build? In the release, I’m well able to reproduce the problem. Assert is triggered in the debug build, maybe it was perceived as a crash?
@igor I was using the debug version. I was running into this issue when looking into another time signature issue can just created this in order not to forget this.
See https://github.com/musescore/MuseScore/pull/5878
Fixed in branch master, commit 4c6a56cfff
fix #299788 removed assert
Fixed in branch master, commit dc654503fa
_Merge pull request #5878 from igorkorsukov/tracker_299788_localtimesig
fix #299788 Crash when deleting a local Time Signature (removed assert)_
Automatically closed -- issue fixed for 2 weeks with no activity.