Score crashes MuseScore

sideways

• May 22, 2016 - 00:03

Reported version

3.0

Type

Functional

Severity

S2 - Critical

Status

closed

Project

MuseScore

Call Stack:
0 Ms::Element::pageBoundingRect element.h 405 0xc27a2e
1 Ms::BspTree::items bsp.cpp 144 0x8fb502
2 Ms::Page::items page.cpp 146 0x7cdd11
3 Ms::ScoreView::paint scoreview.cpp 1906 0x40aba2
4 Ms::ScoreView::paintEvent scoreview.cpp 1690 0x40988c
5 ZN7QWidget5eventEP6QEvent 0x196ac901
6 ?? 0x28c9ec
7 ?? 0x8ec8300
Steps to reproduce:
1) open the attached file
2) navigate to page 6, first measure, bar #40
3) select the first note in the ClsHat: staff (8th staff from the top), an E-flat
4) Notes menu, Transpose..., By Interval, Up or Down, any interval that's not enharmonic E-flat
5) Click OK and it crashes

I tried to reduce the score and make the test case more generic, but I could not. I did this same transpose operation on the notes in the previous page and it did not crash. It's just this note, or maybe all the E-flats in these two measures, and if I cut out the other staves, or cut out the other measures, it does not crash.
This is a bug as of at least 15 days ago.

Attachment	Size
BIYH-DMS-compact.mscz	25.87 KB

Comments

Fyrult

• May 22, 2016 - 01:06

Bad things happen with that score. The transpose dialog is not necessary.
1. steps 1-3 in OP
2. press up arrow, then down arrow.
Result: crash

You can try the same things with the "Kick" or "Snare" underneath.

Can this issue be reproduced from scratch?

sideways

• May 22, 2016 - 02:43

I have not been able to reproduce this in isolation.
I can try to isolate this further, but I can't guarantee it. Maybe someone who is familiar with the code that is crashing can pinpoint it as well.

Marc Sabatella

• May 22, 2016 - 23:02

Status (old)

active

⇒

needs info

I can't reproduce this at all, but I don't fully understand the steps. First of all, all the notes in measure 40 of the CIsHat part are F#, not Eb. Second, I am not clear on if I am supposed to literally select just the note or a range containing the note before doing the transpose. If doesn't crash for me either way, though. Nor does the shorter sequence mentioned in a response.

Is this issue perhaps fixed, or can someone give a more reliable series of steps to crash?

sideways

• May 23, 2016 - 00:28

I just double-checked the score I posted, re-downloaded from this page, and it's an E-flat in bar 40 of the ClsHat: staff, no doubt. It's an octave down F-clef, and the E-flat is in the second ledger line above the staff. Bars 40-41 are all E-flat, but they are surrounded by F# on both sides.

It's not a percussion staff, so there's no fiddling with the vertical note positions. The base instrument is Violincello.

Bar 40, first bar of page 6. @Fyrult reproduced it. I'm not sure what could be so different as to cause the note values to be bogus.

And you can select that one note or that note plus up to the end-of-next-measure. I've tested that much.

Marc Sabatella

• May 23, 2016 - 00:48

Status (old)

needs info

⇒

active

OK, I can reproduce - I was thrown off by the fact that the score starts with measure 0 (I used Ctrl+F to go to the "real" measure 40).

No idea yet what the cause is. We're checking attributes of an element that appears to have been deleted. Based on the names of the staves, are these by chance converted from former drum staves? Perhaps that is part of the key. I'm wondering if it has something to do with there being an accidental on a staff that isn't supposed to have them?

sideways

• May 23, 2016 - 02:07

Yes, I number the pickup bar as 0. It is likely that these were created as percussion staves and converted to Violincello because I was having problems with the percussion staves. Though I might have created new staves as Violincello and then copied/pasted the notes from the percussion staves. One or the other of those two scenarios did occur.

Percussion staves can have accidentals, see the attached files and edit below. The original source of this score is a MIDI file. I imported that into MuseScore, a post Qt5.6 version of MuseScore, then formatted, etc. I wanted most of these staves to be percussion staves, because that's what they are conceptually, but I was having all kinds of problems with that, so I converted to a very stable base instrument selection.

edit: I have attached the MIDI file for this staff, and a .mscz file that was created by opening the MIDI file in MuseScore, then changing the Instrument to Hi-hat in the Staff Properties. As you can see, the accidental is showing up in a percussion staff.