Crash on changing time signature
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
1) Open this score: https://musescore.org/sites/musescore.org/files/2018-12/Reunion.mscz
2) Drag 3/4 time signature from palette to the first measure.
Result: crash
Comments
Another nice scenario:
1) Drag 3/4 time signature to the second measure. This time all goes well.
2) Drag 4/4 time signature to measure 8.
This crashes again, though with a different backtrace.
nice is in the eye of the beholder :-)
In fact I am trying to reproduce the crash on time signature change reported in #279448: Three different crashes. These crashes and the reported one all happen in some functions called by
Score::rewriteMeasures
but I still cannot reproduce the call stack that was reported in that issue.See https://github.com/musescore/MuseScore/pull/4423.
I forgot to change the status in the previous comment.
Fixed in branch master, commit d2f4f5c3db
fix #279593: fix handling spanners on changing time signature
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.