Crash when adding an arpeggio or changing the note value
When pulling an arpeggio on the lower note in a 2-note chord (quarter notes), Musescore promptly crashes every time.
It only does so in the second chord in the bar, on beat 4, not in the same chord on beat 2. (See attached image and mscz file)
Version: 2.0.2
Revision: f51dc11
| Attachment | Size |
|---|---|
| 2015-11-01 16_49_22-MuseScore_ _Documents_MuseScore2_Scores_Laras_Melodie.png | 22.68 KB |
| LM_bugreport.mscz | 42.54 KB |
Comments
Perhaps only a corrupt measure? Try inserting a new one and delete the previous.
It's more serious. Eg select a note of the top staff (or staff below) and change its value (eg a eighth note to a quarter note). Result: crash
More: go in Parts (Part 2 eg, Acoustic guitar). Start playback: curious result. This "playback"result is not unknown for me. I just don't remind immediatly for now...
Which is the source of this file please? Created with the 2.0.2, the 1.3, or imported file (or converted pdf)?
Thanks for the reply.
By deleting and recreating the parts, all seems works fine now ( just need to check two or three things for be sure)
1 LM_bugreport.mscz
So, to know:
the origin of this file, and if created with the 2.0, do you remind some "special" operations related to the parts?
The file was created with the Musescore version mentioned in the first post (2.0.2) a couple of hours earlier and didn't quit in a bad way before the error. (which could have been a cause)
I don't remember any "special operations" on the parts, i just created them using 'new all' and didn't edit them individually at all.
I just copied the faulty measure into an new one inserted before it, now the crash doesn't happen anymore in either of the measures.
Update: Now it crashes when I pull an arpeggio on any eigth note in the second staff, apart from the chords that crashed it before... It also sometimes terminates with a C++ runtime error and then follows it up with "Musescore stopped working". (attached)
The file you have attached to your last comment is the same as before (with corrupted parts, interalia). That you're describing: " I just copied the faulty measure into an new one inserted before it, now the crash doesn't happen anymore in either of the measures" is not absolutely enough for fixing this score.
Have you read my previous comments, seen, open and tried the repaired file ( with parts re-created) in the comment #3 ?
I attach again, it works fine: 1 LM_bugreport.mscz
-------------------------------------------------------------------------------------
NB: and we are always interested in how this score has come to this stage. Eg when did you create the parts? At the very end of the entry of the main score, or before, with corrections, in parts or in the main score, etc.
Any information will be welcome.
And it would be best to indicate how you have done to create this score, step by step. Trying to reproduce this result on another score from scratch.
It wasn't intended as a 'fix', more as experimentation.
I have seen and tried your repaired file and it works fine, thank you.
The score was created with no key, 2/4 time, one staff Violoncello and one staff Acoustic guitar, default length.
After that I:
I created the parts when most of the notes were entered, but changed some stuff after that (mostly lines, articulation, dynamics etc.
I exported the score and the parts to mp3 at some point.
All edits were done in the main score, sometimes in continous view mode (if that matters at all). The parts themselves were NOT edited, only viewed and played.
I can now reproduce from scratch this issue. Report filed soon.
Convoluted issue, involving parts, change of time signature, and finally, the fateful operation, ie the removal of the first measure, which leads to crash and corruption.
And yet, the operations that trigger this result (changing a note value of a certain note and not another, or adding an arpeggio) retains an element of mystery and surprise (why an arpeggio and not another element, considering what I can see for now?)
Maybe this deletion of the first measure (see this issue: #89401: Deletion of the first measure removes the time signature in parts, related?) leads to an underlying corruption (?) which is revealed later by some specific operations, as mentioned above?
One can reproduce this issue from the "fixed" score (see comments #3 and 6, this one: 1 LM_bugreport_0.mscz )
1) Load the file above in this comment
2) Change time signature: 2/4 instead 4/4
3) File -> Parts -> Delete all parts -> "New all" -> Ok
4) Delete (Ctrl + Del) the first measure in main score
(at this step, just before crash, it's a good idea to save the file: Saved score.mscz )
5) Select the F (EDIT) eighth in bass clef top staff , second note (fourth measure), and change the value eg quarter note (or add an arpeggio symbol
Result: crash
6) Reload the file (saved)
7) Message "Restore the session" : Yes
8) View parts, and start playback
Result: corruption on playback and in the score (due also at the presence of another time signature later in the score, see eg the double barlines before the 6/4 time signature)
(accidentally posted to wrong issue, see instead my comment in #89636: Crash on change duration (and other operations) after delete part and insert or delete measure)
(linked fixed to not refer back to this thread :-)
(sorry, messed up twice!)
(three times?!?!?!)
3) File -> Parts -> Delete all parts -> "New all" -> Ok
That's the problem. Duplicate of #89636: Crash on change duration (and other operations) after delete part and insert or delete measure
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.