Crash when glissandos break a certain layout

• Jul 25, 2019 - 23:12
Reported version
3.2
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Hi, the software crashes whenever I try to add multiple bars. It first happen when I tried to add 100 bars in the middle of the song at bar 8. Then it happened at 80, and 50. I managed to do it once with 30 but trying again caused a crash. Now it often happens at 20. I have 100 bars or more to add to the middle of this in order to expand it into a 7 minute song.

Attachment Size
Otonokizaka High.mscz 44.02 KB

Comments

• Jul 26, 2019 - 01:07
Title Crashes when I try to add 20+ bars ⇒ Crashes when adding measures to score.
Frequency Many ⇒ Once
Severity S4 - Minor ⇒ S2 - Critical

Confirmed crash inserting 25 measures at measure 8. Crash report sent referencing this issue.

Also caused crash inserting 15 measures at measure 8. Inserting 10 did not cause a crash. I stopped testing at that point.

I noticed a couple of things. The score is imported from a mxl file and there is a bogus key signature at the measure that causes the crash. Inserting the measures at measure 9 for example does not cause a crash.

Reply

• Jul 26, 2019 - 06:24
Title Crashes when adding measures to score. ⇒ Crash when glissandos break a certain layout

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

Steps to reproduce:

1) Treble staff template
2) Add a note first measure, and another one in last measure + a glissando between them
3) Insert the number of measures necessary for the layout to be organized into one page + a single system on the second page (ie total 216 measures)
(the test file at this step: test glissando.mscz )
4) Insert a new measure (from eg measure 199, but no matter), so which creates another system on the second page.

---------------> crash

Reply

• Sep 27, 2019 - 07:25

Came up again in: https://musescore.org/fr/node/294911

To get the crash in attached file (so, this one: Amazing_Grace_good.mscz)
For example:
1) Load the file
2) In Saxophone Baryton Part
3) Select All (Ctrl + A) + hit arrow Up four times (to change the pitch, just for testing), so first note is now a Bb.
4) Return in main score, and Save (Ctrl + S)

--------> crash

Crash/issue solved by removing the glissandos (6) in main score, measure 65.

Reply

• Nov 4, 2019 - 02:53
Frequency Once ⇒ Few
Reported version 3.2 ⇒ 3.3

Don't know if its related, because this has nothing to do with layout, but simply adding a glissando crashes musescore.
open Blue bossa.mscz (see attachment)
Blue_Bossa.mscz
Select the last note (the G):
LastG.PNG
And double-click on this gliss:
gliss.PNG

EDIT: same for the other gliss:
gliss2.PNG

And I tried removing all system breaks. Same issue. So no layout seems involved.

Attachment Size
Blue_Bossa.mscz 29.01 KB
LastG.PNG 6.38 KB
gliss.PNG 7.22 KB
gliss2.PNG 7.41 KB

Reply

Fix version
3.5.0