Piece plays through 2nd bar of [C2] then crash.

• Apr 1, 2020 - 22:46

I want to hear what I have written in the piano part to check for accidentals.

Go to piano part, press space bar, piece "plays" to end of bar 30,cursor and sound stop, program crashes.

Please see attached:

Also task manager snapshot.
Task Mgr in MS crash.PNG

The high cpu numbers for the "not responding" MS are not static but vary minimally. They seem suspicious but I am limited in my knowledge about that.

Thanks for any help.

Attachment Size
Leaptout 3 264.mscz 37.99 KB

Comments

• Apr 2, 2020 - 09:25

I can confirm that hang (no crash though). MuseScore then monopolizes one core (so 13% CPU load on my 8 core system).
Same in the latest development build.

Reply

• Apr 2, 2020 - 09:48

Output in a Debug build when opening that score:

Debug: in measure underrun 23040 at 240-0 track 17 (...\libmscore\check.cpp:376, void Ms::Measure::checkMeasure(int))
Debug: measure 23040 pos 0, len 1/8, stretch 1/1 track 17 (...\libmscore\check.cpp:324, void Ms::Measure::fillGap(const Ms::Fraction&, const Ms::Fraction&, int, const Ms::Fraction&))
Debug: measure 59040 pos 960, len 1/4, stretch 1/1 track 17 (...\libmscore\check.cpp:324, void Ms::Measure::fillGap(const Ms::Fraction&, const Ms::Fraction&, int, const Ms::Fraction&))
Debug: in measure underrun 23040 at 240-0 track 1 (...\libmscore\check.cpp:376, void Ms::Measure::checkMeasure(int))
Debug: measure 23040 pos 0, len 1/8, stretch 1/1 track 1 (...\libmscore\check.cpp:324, void Ms::Measure::fillGap(const Ms::Fraction&, const Ms::Fraction&, int, const Ms::Fraction&))
Debug: add(Rest): there is already a Rest at track 17 tick 23040 (...\libmscore\segment.cpp:457, void Ms::Segment::checkElement(Ms::Element*, int))
Debug: measure 59040 pos 960, len 1/4, stretch 1/1 track 1 (...\libmscore\check.cpp:324, void Ms::Measure::fillGap(const Ms::Fraction&, const Ms::Fraction&, int, const Ms::Fraction&))
Debug: add(Rest): there is already a Rest at track 17 tick 60000 (...\libmscore\segment.cpp:457, void Ms::Segment::checkElement(Ms::Element*, int))
Debug: Reconnecting broken connectors (2 nodes) (...\libmscore\xmlreader.cpp:639, void Ms::XmlReader::reconnectBrokenConnectors())
Debug: reconnected 0 broken connectors (...\libmscore\xmlreader.cpp:671, void Ms::XmlReader::reconnectBrokenConnectors())
Debug: Reconnecting broken connectors (2 nodes) (...\libmscore\xmlreader.cpp:639, void Ms::XmlReader::reconnectBrokenConnectors())
Debug: reconnected 0 broken connectors (...\libmscore\xmlreader.cpp:671, void Ms::XmlReader::reconnectBrokenConnectors())
Debug: Reconnecting broken connectors (2 nodes) (...\libmscore\xmlreader.cpp:639, void Ms::XmlReader::reconnectBrokenConnectors())
Debug: reconnected 0 broken connectors (...\libmscore\xmlreader.cpp:671, void Ms::XmlReader::reconnectBrokenConnectors())
Debug: XmlReader::~XmlReader: there are unpaired connectors left (...\libmscore\xmlreader.cpp:30, Ms::XmlReader::~XmlReader())

Track 17 would be voice 2 of staff 5 (as far as I can tell, so Piano treble clef

Reply

• Apr 2, 2020 - 11:05

Whow, sharp eyes!

But look at the piano part, those ties are supposed to connect grace notes with the main notes, 2 of these grace notes though exist only in the part but not in the score (and lost their flag too).
So the attached might be the better fixed version?

Whatever: that score definitly is corrupt but MuseScore didn't detect that. Deleting the parts didn't fix it either

Attachment Size
Leaptout 3 264-fixed.mscz 38.1 KB

Reply

• Apr 2, 2020 - 15:04

I was adding the grace notes to access the ties so as to connect the last ending to the main body of the piece so that the last notes before the endings would be seen as extending into the last bar.

I am virtually certain that I was in the piano part when this all happened. I am not certain exactly when the "hat" appeared (the reduction in length of the top tie).

As I remember I add from the top to the bottom.
I added the first one, then the 2nd.
I added all three then made the notes grace notes invisible and selected the top note and moved it to the left to increase the distance to the front bar line, thereby lengthening the tie line. All seemed good until then except for the hat event that I have described.

I then went to the middle note to extend it. It was fine until I reached the same distance as the upper note. When I did a line appeared from the top of the workspace to the bottom. I went back one unit of space and then went to the 3rd note, voice 2.

When I reached the same distance the line appeared again. As an experiment I went a little further, the line disappeared and the top note tie reverted to the hat.

I deleted the grace notes and re-entered them without extending past each other, saved it and then went to playback to check accidentals.

Reply

• Apr 2, 2020 - 16:10

I am now in the score: When I scroll in, the 2 top "grace note" tie lines are there but no grace notes, visible or invisible. I deleted those "free standing" ties and the grace note for voice 2.

I then realized that I was in score format and switched to the piano part where I found the missing 2 grace notes without the tie lines. I then deleted them and saved.

The piece now plays through.
Add top grace note: (I was using the 1/8 grace note but will now use the 1/4 note): I have placed top grace note and added tie, no other adjustment. The program stalls at the same place and crash. Unfortunately didn't save before running. Redone.
I ran it after adding the grace note (no tie) and save - ran with no problem.
Added tie line, saved - stop at same place (end of bar 30) and crash.

Score attached. (The task manager again showed about 30% cpu usage).

Attachment Size
Leaptout 3 264 after crash 2.mscz 36.23 KB

Reply

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