Crash when adding glissandos between notes and rests/to a single note
Reported version
3.3
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.3.0.8737, revision: 4761df6
1) Default score
2) Enter a quarter note
(the test file: glissando.mscz )
3) Select this note and double-click a glissando (so, the glissando is heading towards rest)
------------> Crash
Fix version
3.3.1
Comments
Oops... title reviewed.
Recent regression, October 28, here: 0c1de3d
To fix: #296171: Change of slur direction does not take effect until the next relayout
The previous nightly works, or rather nothing happens (no glissando added, no crash): b6fac5e
As far I recall in the version 2 (at least, the first ones), it was allowed to add a glissando to a single note (ie towards indeterminate end note/rest, as "free" glissandos without a precise end note, behavior rather common in Winds and Strings instruments family)
This was disabled for some reason, and so, now it's a new regression.
See https://github.com/musescore/MuseScore/pull/5460
Fixed in branch master, commit b8eba0fa81
_fix #296566: erase invalid elements from CmdState
Prevents crashes if an element triggering layout has been deleted,
e.g. in case of an unsuccessful attempt to add a glissando to a score._
Automatically closed -- issue fixed for 2 weeks with no activity.