Removing a staff from the score in the instrument menu (Key-i) crashes
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
removing instruments causes Musescore 3 beta to crash.
This is the version:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4133, revision: 0526317
Comments
I cannot reproduce from scratch here with the last revision: OS: Windows 7 SP 1 (6.1), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4253, revision: 082e635
So, for checking, please attach the actual score where you observe this.
Attached the score I am using.
I go to the instruments menu (Key-i) and remove Soprano 2 and Tenor. Then when I click OK to return I get the message "MuseScore3.exe has stopped working".
Confirmed.
Debug output:
Debug: staffIdx out of bounds: LyricsLineSegment (...\MuseScore\libmscore\element.cpp:352, virtual QPointF Ms::Element::pagePos() const)
Fatal: staffY: staves 3: bad staffIdx 4 (...\MuseScore\libmscore\system.cpp:964, qreal Ms::System::staffYpage(int) const)
Does this still happen? I cannot reproduce it with the recent master build.
Still crashes, with the very same debug output
Now I am able to reproduce, it crashes if I zoom out the score to see all pages first.
See https://github.com/musescore/MuseScore/pull/4397 for the fix.
Fixed in branch master, commit 705a94ad7a
fix #279509: always set correct track for spanner segments
Fixed in branch master, commit b487a1b187
Merge pull request #4397 from dmitrio95/279509-spannersegment-tracks
fix #279509: always set correct track for spanner segments
Automatically closed -- issue fixed for 2 weeks with no activity.