7/4 Time Signature Program Crash

• Oct 24, 2019 - 03:30
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Randomly
Status
active
Regression
No
Workaround
No
Project
MuseScore

I'm working on a larger work and there are a few parts where I use a 7/4 time signature. I can create it in the master palette and place it in the score completely normally. however, as soon as I try to add another time signature a bar or 2 bars later regardless of the time signature it crashes the program.

Comments

• Oct 24, 2019 - 03:47

Can you attach the score where this happens. There is probably something else going on because that doesn't normally cause a crash.

Reply

• Nov 5, 2019 - 19:57

I just came across this with a 7/16.

Console output:

Jack appears to be installed on this system, so we'll use it.
QApplication: invalid style override passed, ignoring it.
/tmp/.mount_JysQej/AppRun: line 28: 15355 Segmentation fault      (core dumped) "${APPDIR}/bin/mscore-portable" "$@"

Minimal affected score attached. Interestingly, it only happens when the 7/16 is added to one of the 3/8 measures.

Pop!_OS 19.10, MuseScore 3.2.3

Attachment Size
test-sevens.mscz 12.49 KB

Reply

• Nov 5, 2019 - 20:15

I can reproduce a crash in the this score adding a 7/8 to one of the 3/8 measures, the crash happens in ScoreRange::write when we try to check the endpoint of a slur to see if it is a grace note, and it turns out there is no endpoint but we fail to check for this. So it seems to likely be related to other issues with spanners not being handled properly when time signature changes are involved.

Reply