Crash after adding tremolo to unpitched staff

• Jul 8, 2020 - 03:44
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
Yes
Project
MuseScore

Steps to reproduce in the score:

  1. Add a half note crash cymbal slurred to an 8th note crash cymbal on the next measure (as shown in the screenshot, particularly to staff 26)

  2. Add a 32nd note tremolo to the half note.

  3. It crashes.

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.0.12237, revision: b5add95

Attachment Size
tremolo crash.mscz 39.38 KB
tremolo crash.PNG 33.43 KB

Comments

• Jul 8, 2020 - 10:01

Latest development build (self build in Debug mode) crashes on opening that sample score. Actually it dies of a failed assertion (on save/autosave it seems):

Fatal: ASSERT: "_lidLocalIndices.contains(lid)" in file \libmscore\xml.h, line 276

So the score seems corrupt somehow

In a non-Debug build it won't abort on that assertion, but would certainly fails somewhere later, your case here is just one example

So this here seems to be a duplicate of #307629: Crashing after tying a whole note chord to the next measure or vice versa

Reply

• Jul 8, 2020 - 10:06
Workaround No ⇒ Yes

removing the parts solves the crash, so there's a workaround (which might be the real fix, as with a corrupt part anything can happen)

Reply