Crash when attempting to change time signature
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
1) Open attached score
2) Attempt to change time signature to 9/8
3) Program crashes
| Attachment | Size |
|---|---|
| PlayScore_Violin-a4-02.xml | 69.67 KB |
Comments
The score is corrupt:
Measure 3, staff 1 incomplete. Expected: 0/1; Found: 9/8
Measure 5, staff 1 incomplete. Expected: 9/8; Found: 0/1
After that anything can happen
Better complain to "PlayScore, ReadScoreLib (© Organum Consulting and Dolphin Computing Ltd) Version 3.11" to create software that doesn't produce such corruptions.
Surely a program should not crash whatever the input. I wouldn't like it if my compiler crashed when I made a syntax error.
Still Garbage In, Garbage out. With bogus input and corrupt scores anything can happen. Can for compilers too, when using undefined behavoir
You are correct that MuseScore should never crash no matter what.
That said, I can't reproduce the crash with either MuseScore 3.4.2 or MuseScore 3.5.0 Beta.
You filed this issue under MuseScore version 3.0. That's a really old version. What is the exact version of MuseScore that you're using? (Go to Help | About…, click the Copy revision number button, then paste into a comment here.)
If you're not using a recent version of MuseScore, please download one and try to reproduce the crash using that version.
If you are still able to reproduce the crash, please be specific about the exact steps you're taking when you “Attempt to change time signature to 9/8”.
Still, for a corrupt score you'd need to fix the corruptions first before doing anything else. Ignoring them is goind to lead to trouble later
Oops, accidentally cleared the Frequency.