Crash by switching in Continuous View when a tie extends in another system
Having a score with violin as instrument for 2 staffs (that means, used twice in 2 different staffs). Now I call "edit->instruments" and removing the 2nd staff using violin. If saying OK, mscore crashes.
You can try this in the attached score by removing the Violin for the V2 staff.
This will not happen if only 1 staff uses an instrument, for example if removing the ViolinCello instrument in the VC staff.
Platform: LINUX Fedora 26, x86_64, all updates applied. 1. Satz.mscz
Comments
No crash for me, Windows 7, self built a8efa6d
Which nightly are you using?
Can't reproduce by removing the Violin II (or another instrument) with ec9be4b
oops, mine is a couple days old already...
Needs info, yes
My first guess is this issue, fixed now: #234591: Crash by removing any instrument or staff from a template
Crash -> critical
OK, so let's mark it as a duplicate, unless new Infos come up that indicate otherwise
I'm using MuseScoreNightly-201707281352-master-ec9be4b-x86_64.AppImage
And so, with this nightly ec9be4b, you can always get a crash by removing the Violon II (eg) with your attached score, "Satz" ie: 1. Satz_4_5.mscz ?
Yes, I can.
Well, something is missing.
Can you detailed your steps, ie:
1)...
2) ...
3)
Ok, here I can by deleting the piano (first instrument) and cello (last one) in the attached score.
But I can't reproduce yet from scratch.
Also with: untick "Visible" the piano -> Ok -> Undo
And now, can you with same score (but with all ties deleted, the first one is in measure 42, Violin II) ? : 1. Satz_4_5 ties.mscz
ec9be4b / Windows10
From scratch, steps:
1) Create a score for piano and violin (4 measures only)
2) Enter 16th notes in the top staff until a second system is created, approximately from the middle of the third measure
3) Enter a whole note, measure 3 violin staff, and hit "+" for adding a tie (so it extends to the second system)
- The test file at this step: test piano violin.mscz
- Another one with "Untitled" score 4 measures + flute: test untitled flute.mscz
4) "I" -> Remove the piano -> Ok
Result: crash
- No issue if no tie between the two G in violin staff
It seems the attachment 1. Satz_4_5.mscz differs in some way from my primarily attached 1. Satz.mscz.
My result: crash with 16c32ca using my original 1. Satz.mscz, but not if using 1. Satz_4_5.mscz.
If removing the violin for the Violin staff V1 instead of V2: mscore-16c32ca won't crash.
I found out that I can provoke a crash too if selecting all measures for the V2 staff and then entering the CtrlDel key (I used this shortcut previously for "removing" all measures in the V2 staff)
That is a different issue though, you can't delete a measure of one staff only (just empty it, using a simple Del), Ctrl+Del would delete that measure in all staves, and deleting all measures on one stave would delete all measures of the entire score. So here you experienced #224201: Crash on deleting all measures in a score
Well, there is various ways to get a crash with your score.
The question again is - you have not reply yet: can you reproduce with your score without ties (Satz or Statz 4.5, exactly the same file) in comment #13: https://musescore.org/fr/node/238606#comment-758016
No, MuseScoreNightly-201707301802-master-16c32ca-x86_64.AppImage does not crash if I remove the Violin instrument in the V2 (with edit instruments) staff and confirming with OK!
So, return to square one and steps from scratch: https://musescore.org/fr/node/238606#comment-758176
Sorry for inconvience: I had attached the wrong score: I attached now the right one (from Mozart's little nightmusic), and here, removing the violin from the V2 staff and confirming with OK, lets MuseScoreNightly-201707301802-master-16c32ca-x86_64.AppImage crash.
Please, it's the same issue as described in https://musescore.org/fr/node/238606#comment-758176
The culprits are the ties, especially in your last attach score, the tie in measure 81 (Violin I), the D whole note which extends on another page. 1. Satz_5 ties.mscz
Thanks very much for the hint! But it's not forbidden to make a tie between these 2 notes spanning over 2 pages, I think :-)
I could get rid from my problem by inserting a page break in measure # 80.
Of course it is not, but here it triggers a bug leading to a crash
Who said it was "forbidden to add a tie between 2 notes spanning over 2 pages"? No one.
Remember that you are working with a development version, always unstable and prone to this kind of disadvantage.
And from what I see, there has been a new implementation of the ties and their editing recently.
Keep in mind that the best way to avoid this is to work (especially on scores of this magnitude) with a stable version.
GIT commit 6c735b8/ Windows10
Minimal sequence of steps for reproduce (no need to have two instruments, and to delete something: that was another aspect of this issue)
So:
![tie system.jpg]( "tie system.jpg")
1) "Untitled" score
2) Enter a whole note in measure 4
3) Press "+" to tie another whole note in measure 5 (next system)
4) Switch in Continuous View
Result: crash
This issue occurs on last July 19
So, the most likely here ? https://github.com/musescore/MuseScore/commit/5da44ffd978075d001ecf7c78…
Oops...! :)
Came up again in https://musescore.org/en/node/260446
There I found that there is no stack trace though (not on Windows at least), but a failed assertion:
Fatal: ASSERT: "e == 0 || e->isSystem()" in file ...\MuseScore\libmscore\scoreElement.h, line 384 (:0, )
Came in again (another aspect: see https://musescore.org/en/node/263015#comment-806798) in: #263015: Insert measures causing the extension of ties on a new system causes crash
I can't reproduce this issue. Fixed since three days.
This nightly crashes: 068ad14
Not the next one: 374f9b1
Automatically closed -- issue fixed for 2 weeks with no activity.