Piano Editor crash; crash report attached.

• Mar 5, 2016 - 15:24

The piano-roll editor crashes every time it is used for more than a minute or so. It is intensely frustrating, as there is no other access to note articulation. Here is the crash that just happened (mac crash report, enclosed). I don't hope to hear "not a music-performing program"; released features should not crash.

Thanks.

Attachment Size
PianoCrash1.txt 78.58 KB

Comments

• Mar 5, 2016 - 18:01

If you can post a specific score and precise steps to reproduce the problem, that would be more helpful.

And yes, even though priority remains on notation, we want to fix crashes anywhere they occur. So getting reliable steps to reproduce the problem would be an important step.

Reply

• Mar 5, 2016 - 18:20

I understand; these crashes are all irreproduceable. If you recover the crashed score and make the changes that crashed, it doesn't crash.

I can try to make a dummy score and make successive changes and see if it crashes after five minutes, but I can't imagine it is possible for a human to make several minutes worth of changes in the piano editor accurate enough to be considered reproducible, so we have a problem. I would say edit any score at all, and change notes from 1000 to 1170 length one after the other until it crashes. I guarantee you it will, it's not anything funny I'm doing and it happens no matter what the score. I'll see what I can do.

I would think if you ran the PR editor with a memory-corruption tool enabled, it would find it for you rapidly.

Reply

• Apr 28, 2016 - 22:59

A friend of mine followed my directions to edit his score with the PRE, on Linux, however, and did not experience the unreliability, so I suspect the problem is Mac-specific. Spend five minutes piano-roll editing any score at all on a Mac: change notes to length 960 or 1130, and before five minutes have passed it will crash. I have never ever spent more than five or ten minutes with it on any score without a crash. Obviously, I cannot reproduce five minutes worth of gui gestures.

Reply

• Jul 5, 2017 - 01:00

The piano-roll editor still crashes (on the Mac, El Capitan) vrtually every time I attempt to use this tool, after maybe a minute of changing note-ends. I do have some new information, though.

Before it crashes, every time, you can see that it's ready to crash when the "On Time" and/or "Len" values of the note you are looking at, or a note that you subsequently look at, appear with invaiid values, which are either

  • 0 0
  • 0 2000
  • 2000 2000
  • more rarely, negative values, e.g. 0 -2000
  • in general, anything other than the expected 0 1000 if you haven't edited it

Sometimes, "fixing" them to 0, 1000 works, but as soon as you see these bad values appear, hold your ears, because a crash is imminent. If a trap could be put in for these and other bad values, you might catch the corruption before it crashes. Please try to do something about this bug which has been going on for years now, and readily causes lost work, and raises the bar for phrasing almost beyond usability.

Thanks.

Reply

• Sep 16, 2017 - 04:58

I'm having the same problem with 2.1 version on a PC with Windows XP. Numerous crashes after bogus "On Time" and "Length" values. And now I've noticed that the default values for Arpeggios on the palette have about doubled from the initial installed values. This was after I used the pianoroll to adjust an Arpeggio for a Harp strum and after a crash. Not sure how to reset the palette Arpeggios to original values.

Reply

• Sep 16, 2017 - 05:57

I uninstalled and reinstalled Musescore and things seem to be back to normal, except the pianoroll will still sometimes crash. The pianoroll had really gotten cranky. Will refrain from using it until a later version. It's really a nice feature if only it were stable.

Reply

Do you still have an unanswered question? Please log in first to post your question.