Time Signature Change Crash

• Jul 1, 2019 - 19:26
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
No
Project
MuseScore
  1. Create Project
  2. Attempt to change time signature
Attachment Size
IV. Leo.mscz 23.97 KB

Comments

• Jul 1, 2019 - 19:34
Frequency Many ⇒ Once
Severity S1 - Blocker ⇒ S2 - Critical
Status active ⇒ needs info

Do you want to change time signature in measure 33 (where you are right now in the notes input? )
Can you confirm?

If so, it'a known issue: #283943: Changing time signature on glissando results in crash
And so, to avoid the crash: first remove glissandos which arrive in measure 33, change time signature, and re-add glissandos now.

Reply

• Jul 1, 2019 - 19:40
Status needs info ⇒ duplicate

Well, I think there's hardly any doubt about that. Reopen if it's something else.
So, marked as a duplicate of the mentioned issue above.

Reply