Crash on copy of invalid tuplet

• Jul 16, 2015 - 15:36
Type
Functional
Severity
S3 - Major
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Musescore crashes every time I copy/paste a phrase with sixteenth note triplets from another song. Is there any way to get this fixed?

Here is a video demonstrating the problem

Comments

• Jul 16, 2015 - 15:51

Thanks for the report, but in order to do anything, we need the actual score(s) you are having problems with. You can attach them to a post using the "File attachments" link right below where you type a post.

My guess is it will turn out to be something very specific about the configuration of your tuplets that is triggering this.

Reply

• Jul 16, 2015 - 18:57

I guess that is the score the score you pasting *into*. But in order to reproduce the problem, we would need the score your are pasting *from* as well, and we would need to know which specific measure you are copying.

Reply

• Jul 16, 2015 - 22:24

Thanks, I can now reproduce!

I'm hoping you will tell me this score was the result of an import from MIDI, and that this import happened using 2.0 or one of the earlier experimental pre-release builds. See #57651: Crash on paste of tuplet in imported MIDI file. I believe this is the same basic thing: a MIDI file containing a tuplet was imported incorrectly, yield a somewhat corrupt score that works OK until you try to copy and paste the tuplet.

So assuming this was imported from MIDI, and this was done using something earlier than 2.0.1 - since the bug was fixed by then - we can close this as already fixed. Meanwhile, don't try to copy tuplets from this score; try re-importing the MIDI file.

If you did import the MIDI with 2.0.1, then I guess the bug isnb't completely fixed, so we'd now need the MIDI file too. Or if it didn't come from MIDI, we'd need to understand anything else you can tell us about how the score came to be that might explain the corrupt tuplets.

Reply

• Jul 17, 2015 - 00:46
Title Crashing ⇒ Crash on tuplet with invalid tuplet
Status (old) needs info ⇒ active

Corrupt files can probably create crashes in all sorts of ways. I don't think it's realistic to expect we can prevent all such crashes. Dealing with this one is probably possible, though.

Reply

• May 18, 2020 - 14:16
Severity ⇒ S3 - Major
Status active ⇒ fixed
Regression ⇒ No
Workaround ⇒ No

Fixed most probably since long.
I can reproduce in 2.3.2, but I can't in latest MuseScore version: 3.4.2.9788, revision: 148e43f
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit)

Reply