Crash when changing local time signature to another one with same duration

• Mar 1, 2020 - 16:04
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Apply local time signature 2/2, then 4/4 -> crash

Comments

• Mar 1, 2020 - 17:00
Title Attempting to change local time signature to another one with same duration causes crash ⇒ Crsah when changing local time signature to another one with same duration causes crash

Reply

• Mar 1, 2020 - 17:01
Title Crsah when changing local time signature to another one with same duration causes crash ⇒ Crash when changing local time signature to another one with same duration ==

Reply

• Mar 1, 2020 - 17:01
Title Crash when changing local time signature to another one with same duration == ⇒ Crash when changing local time signature to another one with same duration

Oh drat

Reply

• Jun 3, 2020 - 08:52
Status PR created ⇒ fixed

Fixed in branch 3.x, commit 9d94c33a06

_fix #301834: crash when changing local time signature to another one with same duration

This is because it doesn't check whether the time signature is local or not, so it always goes to every staff and trys to find a time signature segment, causing nullptr._

Reply

Fix version
3.5.0