Select all / copy / paste issues - corruption, hangs, crashes
1. Open Score 1 (produced in 1.3).
2. 'Select All'.
3. 'Copy'.
4. Create piano score with 3 bars.
5. Click on bar 1 rest of the treble stave in the new score.
6. 'Paste'.
7. 'Undo'.
Result: Clefs are missing.
-----
1. Open Score 2 (produced in 2.0).
2. 'Select All'.
3. 'Copy'.
4. Create piano score with 5 bars.
5. Click on bar 1 rest of the treble stave in the new score.
6. 'Paste'.
7. 'Undo'.
Result: Bar rests of treble stave are missing.
Using MuseScore 2.0 Nightly Build (72efce5) - Mac 10.7.5.
Attachment | Size |
---|---|
Undo paste removes elements - Score 1.mscz | 1.42 KB |
Undo paste removes elements - Score 1.png | 17.17 KB |
Undo paste removes elements - Score 2.mscz | 1.52 KB |
Undo paste removes elements - Score 2.png | 34.57 KB |
Comments
I get all sorts of weird artifacts when doing a "select all" and copying and pasting between scores, including corruptions such as this as well as hangs and crashes. I'm going to hope for now the cause is the same and not open new issues. Might be wishful thinking.
#1 - chenlung's example doesn't require 1.3 scores or different scores of different lengths or anything like that. Take demo score, select all, copy. Select first measure, paste, undo. Result same as above - full measures rests are gone.
#2 - same as above, but this time try to paste into measure *2*. Result: hang. Destination is longer than the number of available measures, I guess this isn't being detected after a "select all" as it otherwise normally is (normally pasting a too big selection jus creates new measures as necessary). This may be the same as #30156: Crash when pasting content with final bar empty into score without enough bars.
#3 - similar, but this one *does* require two scores, one made in 1.3, and one in 2.0. Open the 1.3 score, select all, copy. Now create a new score, make it at least one measure longer than the 1.3 score. Click second measure, paste. Result: the music is copied, but so are the initial clefs.
Changed title to better reflect the range of bad effects. Sorry, I don't have the steps to crash, but it results from further experimentation. I'll assume for now that if these other issues are fixed, so would the crash.
https://github.com/musescore/MuseScore/pull/1184
Fixed in 369741ac88
Automatically closed -- issue fixed for 2 weeks with no activity.