Inability to remove vertical frames leads to a crash

• Aug 4, 2016 - 20:47
Reported version
3.0
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

GIT commit: 1736346 / Windows 10

1) "My First Score"
2) Add -> Frames -> Append Vertical Frame
3) Select and Cut this frame

First result: as expected

4) Return to the top of the page: Select and Cut the initial vertical frame (default "My First Score")

Result: unexpected: instead of the removal of this frame, the previous appended vertical Frame is re-created, re-introduced at bottom page.

5) Select and Cut again this appended frame
6) Retun a last time to the top, and Delete only the word "Title"

Result: no more frames. But:

7) Make Undo three (rather four) times

Final result: hang and crash.

-Maybe there are steps shorter. Not found from now.

Comments

• Aug 4, 2016 - 23:46

About two months ago I had an issue with MuseScore 2.0.1 crashing when I tried to delete a vertical frame originally created in the score from the parts. I used the frame to push the music in the score to page 2, but in the parts it was unnecessary and problematic, so I tried to delete it. Every attempt resulted in a crash.

I apologise that I failed to log this issue at the time because the more important problem for me was that my latest revisions had gone missing when MuseScore recovered the previous session and I saved without revising the 'long' file name. (That was eventually resolved when I found those files in the x86 program files directory.)

Could these two crash behaviours be related?

Reply

• Sep 29, 2016 - 10:14
Title Crash when adding-deleting vertical frames ⇒ Inability to remove vertical frames leads to a crash

More precise title with shorter and easy steps to reproduce the crash (with 1ed9da3)

So:

1) "My First Score" (or Treble clef template, after the insertion of a vertical frame)

2) Select and Cut the vertical frame

Result: nothing happens

3) Repeat exactly the same step #2 (so, with the same negative result)

4) Undo twice

Result: the programm hangs.

5) Wait a dozen of seconds
6) Close the score by clicking two times on the "X" (page top right)

Result: crash

EDIT: and as mentioned in comment #2, this issue appears on last June 14.

Reply

• Sep 29, 2016 - 10:25

I can't get past step 4/5, it just hangs there. Self-build in DEBUG mode and in QtCreator's debugger (in the hope to collect a stack trace)

Reply

• Sep 29, 2016 - 12:03

As said, when the programm hangs, wait a little, and close the score with the "X" two times to accelerate the crash to arrive.

Reply

• Sep 29, 2016 - 12:07

as said: I never get there, MuseScore hangs and doesn't respond to any controls, including the X to close a score. I can only kill MuseScore using Windoes' Task Manager or stop it in QtCreator's Debugger, in no case I do get a crash tough

Reply

• Sep 29, 2016 - 12:26

OK, good, that is basically the same as if stopping the Debugger, it is not a (failed attempt at a) clean Exit, by closing tht e score (tzhe + on the score's tab) or MuseScore the x on the musescore window), but a kill of the command.com excuting the nightly.bat.
So no way to get a stack trace and I'm not doing anything wrong in trying to get one ;-)

Reply