Crash on save of file with corrupt parts

• Jul 21, 2019 - 22:13
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
MuseScore
  1. Try to open a Symphony size score with the file name "Roberts'_1st_Symphony.mscz"
  2. Let it load for a bit
  3. Observe as MuseScore decides to spontaneously crash.
    (NOTE: May not work as promised, but I put a lot of work into the file before the constant crashes began)

Comments

• Jul 22, 2019 - 01:14
Frequency Many ⇒ Once
Severity S1 - Blocker ⇒ S2 - Critical
Status active ⇒ needs info
Type Performance ⇒ Functional

You need to attach the problematic score. Use the Choose a file button below.

Reply

• Jul 31, 2019 - 20:00

It always happening is the reproducibility, not the frequency. The frequency is how many times it has been reported and you are the only to report this.

Reply

• Jul 31, 2019 - 21:42

Looks like it crashes on save (including the auto-save), trying to write a completely empty measure. If you view the parts and turn off multimeasure rests, you can see there are some corrupt measures at letter B in the first flute part, perhaps elsewhere as well. So mot likely this happened using an older version of MuseScore before the bug #290546: Copy-paste a part with mm rests on another part/mm rests leads to corruption/crash was fixed.

Solution is to turn off autosave (Edit / Preferences) temporarily, load the score, delete all parts then regenerate them (File / Parts), then turn autosave back on. I've attached a fixed version, this one shouldn't crash.

Attachment Size
Roberts'_1st_Symphony - saved.mscz 339.28 KB

Reply

• Jul 31, 2019 - 21:42
Title MuseScore 3.2.3.7635 Doesn't Want You To Compose Your First Symphony ⇒ Crash on save of file with corrupt parts

(leaving this open for now just in case it turns there is something else going on)

Reply