[4.2 Beta] This score can't be opened with 4.2 but works with 4.1.1, no corruption indicated #20203
Assignees
Labels
Comments
muse-bot
added
crash
cbjeukendrup
added a commit
to cbjeukendrup/MuseScore
that referenced
this issue
Nov 26, 2023
Resolves: musescore#20203 In the score in this issue, there is an Arpeggio with a staff span of 2, which in 4.2 gets converted to a track span of 5. That's fine, but on the staff below the Arpeggio, there is a Rest, so the Arpeggio would end on that Rest. That leads to a crash because of a missing `isChord` check.
|
don't think ive ever seen a bug being fixed this fast, well done |
RomanPudashkin
pushed a commit
to RomanPudashkin/MuseScore
that referenced
this issue
Dec 4, 2023
Resolves: musescore#20203 In the score in this issue, there is an Arpeggio with a staff span of 2, which in 4.2 gets converted to a track span of 5. That's fine, but on the staff below the Arpeggio, there is a Rest, so the Arpeggio would end on that Rest. That leads to a crash because of a missing `isChord` check.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue type
Crash or freeze
Bug description
11258899.zip
When trying to open the attached score with the 4.2 beta, musescore instantly crashes. When opening it with 4.1.1, it works with no apparent issues.
Steps to reproduce
Download the attached score and rename the file extension to .mscz
Open it with 4.1.1 to see that it works without issues
Open it with 4.2 Beta, see that it instantly crashes
Screenshots/Screen recordings
No response
MuseScore Version
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.0-233281140, revision: github-musescore-musescore-23f3925
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Windows 10
Additional context
No response
The text was updated successfully, but these errors were encountered: