Undo after creation of parts with linked staves causes corruption

• Oct 2, 2016 - 14:13
Reported version
2.1
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

Version 2.0.3, AND (exactly the same), with 3.0 under development: 70b00e6 / Windows7 and 10

1) "My First Score"
2) "I" -> Add linked staff -> Ok
3) File -> Parts -> New all -> Ok
4) Undo
5) "N" -> Enter some notes in first (or second staff)

Result: corruption in the other staff (type measure 0/1)

corruption.jpg

- I am surprised myself to find this issue now. Before the 2.0.3 release, I thought to have looked a lot this question of parts and linked staves.
Not enough, apparently, arhhh ... (very) disappointed! Bump... :(

NB: of course, for avoiding the step #2, you can choose first the "Guitar + Tablature" template, and then step #3, etc.

Comments

• Oct 2, 2016 - 20:39

It's pretty incredible, this issue goes back more than 2 years! Two or three days before the release of the Beta1 (ie, 2014, August 26)!
I continue the focus, and more info soon, I hope.

Reply

• Oct 2, 2016 - 21:56

So, I confirm this issue occurs on August 24, 2014

I checked before: from May 2014, June and July 2014, all it worked.

I have checked after, with several nightlies of end 2014, 2015, 2016 (especially February and March).
I can still check a little, but I notice I've never seen this issue fixed since August 2014, and possibly broken, then re-fixed, re-broken, etc. No, only one shot, from what I see by now.

So, this nigthly works: fdd67f5
Result:
24aout 57dd.jpg
Not this one: b549f6f (the last one of August 24, and four commits after the previous mentioned nightly):
Result:
24aout b549.jpg
Just before this nightly, I see this commit: https://github.com/musescore/MuseScore/commit/fe96bf6b47dc6fe9ef41d9829…

For fix: #30671: Crash after "n+1" insert measure operations after undo of add part in score "n" measures long

Useful checking by more authorized persons than me, of course, but rather a good candidate, right?

Reply