Crash on saving due to corrupt part

• Apr 20, 2020 - 12:08
Reported version
3.4
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
MuseScore
  1. Open existing score currently working on, select Concert Pitch
  2. Select the bar I wish to input (in this case Trombone 2)
  3. Select Enter - note value (semi-breve)
  4. Enter note (D)
  5. Select articulation (accent)
  6. Repeat 4 and 5
  7. Select both bars and manually change notes to octave higher via arrow key
  8. Deselect the bars
    9 Click on save - it immediately crashes
    I have restored factory settings, uninstalled then re-installed, cleaned up my computer using CC Cleaner, deleted duplicate files in Musescore folder. Still crashing Can't Take My Eyes Off You.mscz

Comments

• Apr 20, 2020 - 12:11
Frequency Many ⇒ Once
Type musescore.org ⇒ Functional

Confirmed.
Score stems from 3.2.3 (so you should update), but crashes (for me) in 3.4.2

Reply

• Apr 20, 2020 - 12:41

Delete the parts and then re-create them.

In general I find it is always better to enter everything into the score first and only then create the parts. Then I restrict my editing of the parts to tidying up the formatting. If I need to change notes I do it in the score. There are numerous reports of crashes which seem to be related to score and parts not always keeping in sync and I seem to manage to avoid them using this workflow.

Reply

• Apr 20, 2020 - 12:56
Status fixed ⇒ active
Fix version 3.5.0 ⇒  

True, none of those complex steps are needed, just open and save.

It still crashes in a debug build BTW, on a failed assertion:
Fatal: ASSERT: "first()" in file ...\libmscore\measure.cpp, line 1916

Reply

• Apr 20, 2020 - 13:16

Hmm, doesn't crash in a Release build though (actually MSVC RelWithDebInfo) but does in Debug (actually MinGW Debug), guess that assert is just disabled there.

Reply