The collision of editing handles (start/end) of certain lines with vertical frames crashes the program
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Version 3.6.2 / Windows10
Unexpected and accidentally discovered issue. I'm not sure if this kind of use of lines editing in correlation with vertical frames occurs in real life (or by chance... maybe), but it's worth mentioning.
Steps:
- Default score (i.e. with a vertical frame already in place - same if a vertical frame is inserted later)
- Add some lines: text lines, straight lines, crescendos/decrescendos ...
- Single click on a line to enter edit mode, then click again on the start or end edit handle.
- Drag upwards with the mouse or the arrow keys
Result: When the handle meets the frame, the program shuts down
Test file: frames lines.mscz
See:
Comments
I can reproduce with 3.6.2, but not with a self build based on the 3.x branch (with quite a few changes on top)
So I guess this issue here is a duplicate of another one that got fixed meanwhile (but not yet released)
I don't see any likely candidate though, maybe it got fixed 'by accident' as a side effect of some other fix
3.x crashes on ot too, with a failed assertion:
Fatal: ASSERT failure in QList<T>::operator[]: "index out of range", file C:/Qt/5.15.2/mingw81_64/include/QtCore/qlist.h, line 575
Found it, #322957: Dragging the ends of trills causes measures to move around erratically the fix for that, https://github.com/musescore/MuseScore/pull/8600 fixed this issue in a tangent (?).
(Phew, this saved me from having to do a lengthy
git bisect
)In reply to Found it, #322957: Dragging… by Jojo-Schmitz
Yep I could have told you I'd fixed that just from the description!
It just took you way too long (for my notorious lack of patience) ;-)
Automatically closed -- issue fixed for 2 weeks with no activity.