Undetected error condition causing application crash with no information.

• Jun 15, 2023 - 05:29

I recently had a difficult situation while transcribing and old POP song. Near the end of entering the music Musescore 4 crashed and abended without any information as to why.

Firstly, Platform & version information:
- Windows 10 Version 2009, Arch.: x86_64,
- MSI Gaming laptop with 16 Gbyte of installed RAM
- MuseScore version (64-bit): 4.0.2-230651553, revision: dbe7c6d

I was transcribing the song Donna (by Ritchie Valens). I set up the file properties, entered the notes, then ornamentation (ties, slurs, breaths, etc), and entered the lyrics. So far so good. I was entering the chords and successfully got to the end of measure 31. I then entered the F at the start of measure 32 and touched the spacebar to move the cursor and the application abended (right out to the operating system) with no error information. This abend occurred every time I retried to enter the F chord symbol. After a whole bunch of frustration, I found that I had forgotten to enter the "end of repeat" barline at the end of measure 12. Once I found my mistake, I entered the end of repeat symbol into measure 12 and all is well.

I have attached the successful version of the song and hopefully with the description above the problem should be repeatable.

My frustration is that it took a bunch of time to find as there was no hint as to the error that caused the abend. Just crash and gone. Is it possible to detect the second opening repeat symbol without an intervening end of repeat symbol?

Attachment Size
Donna (4).mscz 2.34 MB


I can't reproduce a crash with chord symbols from just what you've described, but if you give precise steps to follow with this score, we can try to confirm.

I can confirm a crash deleting the repeat from bar 12. Howeve,r no crash in current development builds of 4.1, so it seems that might have been fixed already.

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