crash when inserting time signature in corrupt score

• Jan 3, 2016 - 22:24
Type
Functional
Severity
S3 - Major
Status
closed
Regression
No
Workaround
No
Project

musescore 2.0.2, win 10. crash when inserting key signature, from 3/4 to 5/4.
GIT commit: f51dc11


Comments

In order to help, we need you to attach the score you are having problems with and give order steps to reproduce the problem.

It's possible you are seeing the effects of a bug already fixed for the next release: [#74861]. Workaround is to select the measure, not the rest.

I'm afraid this score appears to be badly corrupted, in some rather unusual ways I don't recall having seen before.

For one thing, try going to tab for the Alto Saxophone part and clicking the first measure after the multimeasure rest. See how the status line reports this is measure 10, even though the rest is twelve measures so this should be measure 13? There are further discrepancies as you work further through the score, such that by the time you get to the last measure before the final multimeasure rest, it reports as measure 51 when it is really measure 66.

It is the discrepancy in measure counts that is causing the problems. The workaround will be to delete the parts and recreate them.

Still, we would like to know if you have any insight into how this might have happened. One thing I notice is that the original parts don't appear to have time signatures. This is probably the result of #89401: Deletion of the first measure removes the time signature in parts or something similar. Not sure if that will turn out to be the root cause or not.

Title crash when inserting time signature crash when inserting time signature in corrupt score
Status (old) closed needs info

I'd still like to understand how the score got into this state in the first place, though. If it happened once, it could happen again.