System freezes on playback when start repeat in coda is missing

• Jun 27, 2015 - 20:29
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

How to reproduce this error:
- Create a new file
- Insert a D.C. al Coda and a Coda
- In the Coda, add an end repeat in the last measure, but no start repeat

A file with this steps done is can be found in the attachements.

Expected behaviour:
This situation happened on accident and isn't logical, so the playback should just stop at the end of the coda

Actual behaviour:
A click on "Start or stop playback" or "Rewind to start position" makes MuseScore freeze, MuseScore starts to take up more and more memory and has to be killed, else the whole computer will freeze.

Guess: the missing start repeat ends into an infinite loop. Looks a bit similar to https://musescore.org/en/node/17445

System: Debian Jessie
Version: 2.0.1
GIT commit: b25f81d

Attachment Size
crash_missing_start_repeat_in_coda_on_playback.mscz 3.31 KB

Comments

• Jun 27, 2015 - 22:12

This appears to have already been fixed since the release of 2.0.1, as I cannot reproduce. there were a number of fixes relating to playback of repeats, so I can't say which might have fixed it.

You might want to try out a nightly build and veirfy it is fixed for you, and it isn't just a case of it working on a debug build but not a release build or soemthing like that. FWIW, I tested on Ubuntu using a debug build.

BTW, your score also will not play as expected because you have a coda "marker" rather than a "jump" at the end of measure 1. You need to use to the "To Coda", not the coda sign itself, ot trigger a jump. You can always change the text of the marking to be just the coda sign if you prefer, but you have to use the "To Coda" from the palette.

Reply