musescore / musescore/MuseScore
Crash when changing dynamic in a score that is corrupt but not detected as such
Open
Nobody has claimed this yet.
corruption
needs review
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Describe the bug
Originally reported in https://musescore.org/en/node/343454.
- Download the attached broken score
- In measure 26 in the voice (tenor) part, delete p marking and add a new dynamic in that location
-> Crash
The score is clearly corrupted, but this is not detected.
Punta_Patri Musescore 4 - does not yet crash.mscz.zip
Punta_Patri Musescore 4 - does crash.mscz.zip
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the two attached .mscz.zip scores in MuseScore and reproduce the edit in measure 26 of the tenor voice: delete the existing p marking and add a dynamic at that location. Compare the behavior of the two files and trace the dynamic-editing path until the corrupt score is detected; done means the edit no longer crashes and the corruption is handled visibly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100