Copying voice 2 notes with beams causes crash

• Dec 15, 2018 - 21:45
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
Yes
Project
MuseScore

Every time I try to copy and paste notes on top of previously composed notes, it freezes and then force closes the program. It is frustrating since I have to make sure my work is saved every two seconds.

Comments

• Jan 8, 2019 - 23:38

I have the same problem, but I would add the following: in my case, not only does MuseScore 3 crash when copy-pasting over existing notes, it always crashes after one successful paste, regardless of whether that was on top of existing notes or into a blank measure.

My environment:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4785, revision: c1a5e4c

I have tried the following:
Cleared the Windows Clipboard - no effect
Cleared the Office Clipboard - no effect
Cleaned the cache with CCleaner - no effect
Restarted the computer - this successfully ‘reset’ MuseScore 3, but again, only for one Copy-Paste; then the problem re-appeared

I am sending a score where this happens on my machine. I want to copy measures 19, 20, 21 and 22 of the right-hand piano part and paste them into measures 27, 28, 29 and 30 of the same part.

I will be happy to look at Event Logs if someone will tell me which ones I should look at.

Attachment Size
Marchesi_Vocalises_Op._15.mscz 24.03 KB

Reply

• Jan 9, 2019 - 00:25
Title force shut down when trying to copy and paste ⇒ Copying voice 2 notes with beams causes crash
Severity S3 - Major ⇒ S2 - Critical
Status needs info ⇒ active
Workaround No ⇒ Yes

As I suspected, the problem is related to #281154: Crash with first note of measure set to beam middle and nothing to beam to.

I got the same crash as you. I then set the beaming for the initial rest and eighth notes in measures 20 & 22 expecting the crash to not happen, but it still crashed. I then set all beams to none and the copy was successful. I was then able to adjust the beaming.

A difference between these two issues is that this score was created in version 3. A similarity is that MuseScore is figuring out how to display the beams in each situation (during import in the other issue and during paste for this issue).

Reply

• Jan 9, 2019 - 02:26
Priority ⇒ P0 - Critical

Thanks for the analysis! Sounds identical then - as I already observed in the other issue, it isn't about 2.x import as I could reproduce in a score created from scratch. But we'll keep this open to be sure the same fix really does do the job.

Reply

• Jan 9, 2019 - 03:30

What made me doubt that it's the same issue is that when you import the score, changing the middle beam that doesn't connect to a start beam prevents the crash.

In the attached score I'm not sure which note is causing the crash since I didn't go note by note, but I made sure all middle beams had something to connect to or changed to start beam, at least that was my intention during testing. When that still crashed, I simply turned all beams to No beam and the crash on paste stopped.

Reply