Copy and paste empty measures with different time signatures and in a certain order causes a crash
Nigthly October 23 (fc3ea8e)/ Windows7
1 Reproduce exactly the following sequence. From "My first score"
2 Copy and paste on the following measure, or one of the followings
Result: crash
Additional notes
-If you copy and paste the same sequence after filling the measures, there is no crash.
- If you copy and paste the first six measures (so, not with the 9/8), there is no crash
- If you keep this 9/8 measure, but remove (Ctrl + Del.) the second empty measure , there is no
crash. But if you insert a new measure 2 (the second in the score), then again there is a crash.
- If you keep the same sequence of time signatures, but replace the last 9/8 measure (by 3/4, 6/8, C, or whatever, I think I made the detail), then there is no crash.
So it seems that only this 9/8 timesig or measure (in this sequence) is involved. Strange, is not it?
And if you add in this sequence a new timesig (e.g. 3/4) after 9/8, there is no crash!
So it's really a case particularly difficult, tricky, and it is not certain at all that it shall verified and reproduced in real life (of MuseScore)! But we had to report it.
Maybe there has a "minimal" crash, but I have not found yet.
Attachment | Size |
---|---|
sequence1.jpg | 21.78 KB |
copy-paste sequence1.jpg | 22.78 KB |
Sequence2.jpg | 16.63 KB |
Séquence3.jpg | 16.78 KB |
Comments
After checking, I can only say that this issue (with the exact same sequence) occurred between:
-August 11 and this Nightly, correct:
https://github.com/musescore/MuseScore/commit/0c44719a588c505f94c0c7734…
- and August 17, and this one, with crash:
https://github.com/musescore/MuseScore/pull/1135
Unfortunately, between these two dates, there has been, as you know, a font problem (qt.conf) that prevented any use of Nigthlies. So my help stops here :(
I think it's a duplicate of #35851: Crash when pasting measures in another measure with different actual duration
I can reproduce the crash you describe in the current report with MuseScore fc3ea8e but not with the pull request (comment 4) fixing the crash described in the report 35851.
Good new! Copy-paste ok. I cannot reproduce the crash, as you see.
This issue has been certainly fixed by this commit: https://github.com/musescore/MuseScore/commit/7c3856551d4e17f36ff074e33…
So, we may close this issue :)
I was wondering if the other recent copy/paste fix would have fixed this one too - thanks for checking!
This is what is called kill two birds with one stone!! :)
Automatically closed -- issue fixed for 2 weeks with no activity.