Crash when changing Time Signature in parts

This happens on my score as well. Is there a workaround for this?

The workaround is to not create parts until the times signatures are all entered.

I can confirm the crash, it happens in breakCrossMeasureBeams(), in measure 20 (!), because the measure seems completely empty, no rests or anything. Only thing I can think about that measure that would be special is that might be where the line break occurred, as this was the case for #282503: Spurious line break after removal of line break on previous system. Would seem unexpected if these two apparently unrelated bugs turned out to have the same cause, but you never know.

Do NOT change the time signature!!!!! That simple!

It's a workaround if you're wondering.

No, the workaround is to not create parts, or delete them, prior to changing the time sig

Came up again in #282840: Deleting something near a triplet; also tempo as well

And once more in: https://musescore.org/fr/node/284303

Very bad things here (well, more or less expected since you get crashes)
Nevertheless, for example:

1) SATB template (entire, or with a few measures)
2) Create parts
3) In Soprano part: insert a 2/4 time signature
4) Toggle in other part let's say Alto (press M to disable mm rests)

Result: caracterized last measure corrupt, and very bad corruption (0/1) in parts, and on Save, in the entire score. See the test file: satb time sig parts.mscz

Really critical.

After checking, and in the scenario just above, I observe a change on August 14, 2018.

• As expected with d56efb5
• And things turn wrong with a7a1a56
  (nothing obvious at first glance - there is another commit between them - at least about time sig only)

Came up again in #285344: MuseScore crash saving after add Time Signature on a part

See https://github.com/musescore/MuseScore/pull/4781.

New pull request: https://github.com/musescore/MuseScore/pull/4783

Fixed in branch master, commit ab4704cf44

fix #282275: Crash when changing Time Signature in parts

Fixed in branch master, commit 2c21b2a309

_Merge pull request #4783 from mattmcclinch/282275-change-timesig

fix #282275: Crash when changing Time Signature in parts_

Fixed in branch 3.0.5, commit 8d61f4f987

_Merge pull request #4783 from mattmcclinch/282275-change-timesig

fix #282275: Crash when changing Time Signature in parts_

Automatically closed -- issue fixed for 2 weeks with no activity.

I have a piano score I'm working on (thus, just one part) in which trying to change a time signature anywhere crashes MuseScore. Attaching file below. This is on macOS Sierra (10.12), Arch.: x86_64, MuseScore version (64-bit): 3.2.3.22971, revision: d2d863f.

See: https://musescore.org/en/node/282244#comment-954547

EDIT: please open a new issue if necessary. Your score has not parts (it's only the main score: you can create parts via menu "File" -> Parts), so, it's the wrong place to report this issue.

I am finding this same issue, when I attempt to change a time signature, Musescore crashes. My score is a scanned PDF which I am now trying to correct the scanning errors of. So parts are already fully created but the time signature change has not been recognised during the scan, so I want to add it in. I don't fully understand the replies here to know if someone has found a solution?

Since this issue is closed, it's not the same as yours. Post your PDF in the forum at https://musescore.org/en/forum/6 and someone will help you if they can.