Musescore crashing at first attempted edit after opening larger concert band score

• Feb 4, 2020 - 03:04
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project

I've been re-writing a condensed concert band score into a full score for ease of use, and today after updating to the latest update (3.4.1.25011) I found that whilst I could open the score, it would crash if I tried editing anything. Repositioning a dynamic marking, changing the header of the score, changing the pitch of a note - all results in a crash. Even just opening this one score and leaving it sitting there will get a crash after about 5 min.

Setup:
MacBook Air running Catalina (10.5.2)
1.4GHz Dual Core i5
4GB RAM

Troubleshooting I have tried:
- Rebooting system
- Re-installing Musescore from website
- Tried different score (single page of music) - does not crash, allows editing.
- I save my scores to iCloud Drive (for use between multiple systems), but I also copied the score to my desktop and opened it from there - no improvement.

I will (tomorrow, once I'm home again) throw the score against my iMac as it has a bit more power, and see if anything changes.

I've attached a copy of my score as well as the crash report my computer spat out - not sure if the second is of any use.

Let me know if you need anything else!

Attachment Size
Bandology.mscz 306.65 KB
Musescore Crash.txt 103.36 KB

Comments

I think it may have been a corrupt file - I was able to export the score as a .musicxml file and import it back into MuseScore and successfully start editing.
Lesson learned for extra redundancies!

Opens just find, but crashes in (auto)save, most likely cause is a corrupt part, so remove those and regenerate

Edit: indeed, and this time the first I tried: the Piccolo. I removed that part and recreated it, fixed score attached

Attachment Size
Bandology.mscz 304.12 KB