Changing time signature on glissando results in crash
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
3.0.2 / Windows7
1) Default score (or open the test file: glissando time signature.mscz )
2) In two first measures, enter two whole notes + glissando
3) Select the second measure
4) Double-click time signature 3/4 in the palette
----> Crash
Fix version
3.3.1
Comments
Workaround: remove first the glissando before changing time signature (and so, re-add glissando after that)
Came up again in https://musescore.org/fr/node/284204
For the record, always active in 3.0.5 and master 75a6a85
I note we currently lose ties when adding a time signature change - see #277800: Adding time signature breaks a tie across barline. Although that's certainly not ideal, it beats a crash, so for now I'd settle for just deleting the glissando if it's too hard to re-establish (I could see it being complicated if it's a full score and there are lots of them, some cross-staff, etc).
Came up again in #291627: Time Signature Change Crash
(for the record, change time signature in measure 33 containing glissandos)
See also: #292631: Crash when glissandos break a certain layout
Cross-note tremolos have (looks like) a similar problem. See https://musescore.org/en/node/288576#comment-950224.
This issue is actually caused by a crash when deleting a measure which ends with glissando crossing its start. This PR should fix it: https://github.com/musescore/MuseScore/pull/5394.
The fix does not fix the tremolo issue mentioned above.
In reply to This issue is actually… by dmitrio95
The tremolo issue is already taken care of in PR #5383.
https://github.com/musescore/MuseScore/pull/5383 is for #288576: Strange results when changing 4/4 measues with halfnotes tremolos between notes to 3/4, not sure whether that also fixes #292631: Crash when glissandos break a certain layout?
Fixed in branch master, commit 1e522744c1
_fix #283943: fix a crash on deleting a measure at glissando end
Remove glissandi crossing the deleted measure range like it is done
currently for ties._
Fixed in branch master, commit e924baaa92
_Merge pull request #5394 from dmitrio95/283943-delete-measure-end-glissando-crash
fix #283943: fix a crash on deleting a measure at glissando end_
Automatically closed -- issue fixed for 2 weeks with no activity.