Crash by removing parts when creation of other parts is undoing

Two observations:

1) This inability to remove parts, when corrupted, goes back to:
- February 26 (Branch: master). It is possible with this nightly: bec7074,
not with that one: c6ccf18
So, the same commit: https://github.com/musescore/MuseScore/commit/8bf08c232818e04150481ceb2…
- and March, 29 (for Branch: 2.0.3), just some days before the release of the 2.0.3.
I guess here: https://github.com/musescore/MuseScore/pull/2489/files

2) The workaround, as mentioned in the first link, is to export the file in the MusicXMLformat: via this format, the parts are not exported, which is an excellent way to remove them! Then import this xml file, re-create parts, and all is well.

Of course, it works also with the 2.0.2 (released in July 2015, and checked on nightlies of this day and period, and followings, so until end February 2016).
But nobody may have/use the 2.0.3 and the 2.0.2 both. The export via the XML format avoids this problem.

Okay. I did not know about portable apps, and I did not use them.

Well, not really necessary, because the 2.0.2 is only a nightly "stopped in the time" of July 16, 2015, that's all. And one, is very few! But good to know for these portable apps.

Ok, found/understood this issue.

I can therefore reproduce a file whose corruption (when it is located in the parts) is not detected by 2.0.3.
And another one whose corruption is reported in the dialog box (because it is in the main score)

The point common to these two files is that they crash when you want to delete the parts.

And as if by chance, as I indicated in comment #1, this crash, by deleting parts, comes after end February 2016 (and therefore the 2.0.2 is not affected by this, or nightlies of the following months)
So, I think I've won the jackpot!

So, to reproduce from scratch:

First scenario

1) "My First Score"
2) Generate parts -> New all -> Ok
No necessary to enter notes, so, we continue
3) Generate parts again -> New all (or New -> Tick "Piano") -> Ok
4) Undo
5) Enter notes in the main score
6) View Part -> Press "M"
Result: corruption (which may easily leads to crash of course)

7) Save -> Close
8) Reload
The test file at this step: Test file parts 1.mscz
Result: you observe the corruption is not reported by the 2.0.3

9) File -> Parts -> Remove the part -> Ok

Final result: crash

Second scenario:

Same 4 first steps, ie:
1) "My First Score"
2) Generate parts -> New all -> Ok
No necessary to enter notes, so, we continue
3) Generate parts again -> New all (or New -> Tick Piano) -> Ok
4) Undo

Then:
5) Enter notes in the part
6) View main score
Result: corruption

7) Save -> Close
8) Reload
The test file at this step: Test file main 2.mscz

This time, the corruption is reported via a dialog box (-> Ignore)

9) File -> Parts -> Remove the part -> Ok

Final result: crash

For the record, this issue #126916: Undo after creation of parts with linked staves causes corruption conducted me to understand this one.

I can't reproduce this issue.
Fixed by: https://github.com/musescore/MuseScore/commit/c143ce2ad5047edb580c84e2a…
Thanks.

EDIT: more exactly, I can't reproduce from scratch with this nigthly a61cf1c, since there is no more corruption after undoing the creation of parts.
But with the same nigthly, the test file attached to the comment #8 (with the corruption in main score) crashes when loading: Test file main 2.mscz
And the first one (with the corruption in parts) leads to a crash simply by pressing "M" when you open the part: Test file parts 1.mscz

This issue is a mess, but https://musescore.org/en/node/139071#comment-604656 should be fix together with #126916: Undo after creation of parts with linked staves causes corruption indeed. The top issue is still a problem probably and https://musescore.org/en/node/139021 need fixing.

In current 2.0.4 branch, I can open and delete parts.

Automatically closed -- issue fixed for 2 weeks with no activity.