musescore / musescore/MuseScore
Score corrupted after I done some minor changes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Describe the bug
My score is perfectly intact before I adopt some minor changes. After I adopted those changes and saved them, the next day I discovered that I could not open my score again. I have forgotten what exact changes I have adopted, but I'm sure it's some small changes to the last intact score.
Fortunately, I have a version control system running on that score file. Therefore, I could provide the last intact score and the first corrupted score. Below are the scores.
scores.zip
To Reproduce
Steps to reproduce the behavior:
- Open the intact score and do some specific changes (I have forgotten what exact changes I have adopted)
- Save the score and close the MU4
- Reopen the score
- MU4 pops up an "Open error" dialog showing that my score file is corrupted
Expected behavior
The score can be successfully opened with no corruption appearing.
Screenshots

Platform information
- OS: Windows 10
- Musescore 4.0.1
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
Start with the attached scores.zip and compare the last intact score with the first corrupted score. Try reproducing the failure in MuseScore 4.0.1 on Windows using the reported save-and-reopen sequence, then identify the affected score data and confirm that the corrupted score opens successfully without the error dialog.
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
- Needs clarification
- Newbie friendliness
- 25/100