Crash by editing/selecting entire score when another hidden staff contains beamed notes
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Musescore crashes when I attempt to lower an instrument part by one octave when the other part is hidden.
Steps to reproduce:
1)Open the attached file in Musescore 3
2)Load up the instruments dialog box
3)Uncheck the visible checkbox for instrument no2
4) Now only part 1 is visible. Select all using Ctrl+A
5) Attempt to lower everything by 1 octave using Ctrl+Down arrow key
6) Experience a crash
| Attachment | Size |
|---|---|
| Sur_le_pont_d'Avignon_duet.mscz | 22.01 KB |
Fix version
3.1.0
Comments
Confirmed. Not sure what the trigger is exactly, but the crash happens when processing the selection, I think a beam belonging to the invisible staff is still selected perhaps?
I cannot reproduce here, Windows7 (with 3.0.2, or a current dev. version 343d2f4)
After step#5, I get the expected result, see image below. And no matter other added octaves up or down (and several new attempts)
What OS?
If dev. version (nightly), release build or self build?
EDIT: but I can reproduce constantly with Windows10 (3.0.2 or 3ba972d)
Surprising.
In reply to I cannot reproduce here,… by cadiz1
I've tested this using both the repository build (3.0.0) and the Appimage (3.0.2) on Manjaro Linux. FWIW this example was originally a Musescore 2 File which I opened and converted to Musescore 3 format. I've no idea if the bug reproduces in Musescore 2, however.
I can reproduce it from scratch (with Windows10).
As Marc thought, beamed notes are involved. I see something that was really unexpected in October. Then it seems solved later in the month, but it is followed by random crashes (for me anyway). I'll try to explain more, but I won't have one definitive clue right now.
The main point: this configuration
![beamed.jpg]( "beamed.jpg")
(the test file: test beam.mscz)
Simply remove the two eighth notes for a quarter note, and the issue is solved: changing octave works as expected with the remaining visible staff.
But, until October 22, 916c402, by uncheking the 2nd instrument "Visible", I get (but no crash as far I know after a few attempts)
![beam.jpg]( "beam.jpg")
![flute.jpg]( "flute.jpg")
On 24 october, 8a42030, the second instrument is really hidden. Maybe after this fix? https://github.com/musescore/MuseScore/pull/4032/files
After that, I can no longer find where a crash can inevitably or not occurs. Maybe another issue (or underlying issue) has been added to it later, but I can't determine that at the moment.
Always active with the 3.1 beta.
Other scenarios (but the trigger is always the command Ctrl + A)
1) Load the test file: test beam.mscz
2) "I" -> Hide the second staff -> Ok
3) Ctrl + A
4) Change the pitch of the whole note (eg Arrow Up)
---> Crash
1) Load the test file
2) "I" -> Hide the second staff -> Ok
3) Ctrl + A
4) Press "I" again
-----> Crash
https://github.com/musescore/MuseScore/pull/4945
Fixed in branch master, commit 88bc651eae
fix #284012: Crash by editing/selecting entire score when another hidden staff contains beamed notes.
fix #287515: Crash on changing notes after transposition.
Fixed in branch master, commit 6c58cef177
_Merge pull request #4945 from songchaow/fix-287515-crash
fix #284012 and #287515: Crash by editing/selecting entire score when another hidden staff contains beamed notes_
Automatically closed -- issue fixed for 2 weeks with no activity.