Crash by changing time signature in a measure in Continuous view when a glissando extends from the previous measure

• Feb 14, 2017 - 09:00
Reported version
2.1
Type
Functional
Severity
S2 - Critical
Status
closed
Project

Version 2.03, and current 2.1 dev. 23b060d / Windows7

1) "My First Score" (or load the test file, here at the step 4: test file.mscz )
2) Toggle in Continuous View
3) Enter a whole note in measure 1 and another note in measure 2
4) Add a glissando.
You are here:
glis.jpg
5) Add a new time signature eg 3/4 into the measure 2
gliss1.jpg
6) Save as -> Give a name -> Save

Result: crash

7) Try to reload
Result: Load error warning (Cannot read file...)
Right-click to the file -> Properties: Size: 0 octet (s)

The test file at this step: file after crash.mscz


Comments

Title Change time signature on a measure on continous view when a glissando extends from the previous mesure causes a crash Change time signature in a measure on continous view when a glissando extends from the previous mesure causes a crash

You can observe:

. First point:
With the same initial attached file: test file.mscz, you can get a crash at step #5 (before Save) by toggle in "Page View"

. Second point:
With this file: test file Page View.mscz and with steps:
1) Load the file above
2) Add a glissando between the two notes
3) Change time signature in measure2
4) Toggle in "Continuous View"

Result: the glissando extends to the end of the file
glis2.jpg

Title Change time signature in a measure on continous view when a glissando extends from the previous mesure causes a crash Crash by changing time signature in a measure in Continuous view when a glissando extends from the previous mesure

So, from what I see by going back in time, this issue is a two-stages rocket.

Chronologically, the first issue/stage occurs on February 18, 2015, and leads to the two results described in comment #2 , ie:
- the first one: crash when switching from Continuous View to Page View
- the second one: glissando extending to the end of the file when switching from Page View to Continuous View. Knowing we can see the same behavior, to a lesser extent, in Page View under certain conditions of layout.

- This nightly works: e7591d1
- Not this one: 802fa8a

There are three commits between these two nigthlies. So, I presume this one might be a good candidate? https://github.com/musescore/MuseScore/pull/1536/files

The second issue/ stage appears on July 8, 2015, and leads to the result reported initially, ie crash by saving the score, with deletion of all data.

- With this nightly, there is no crash: e5f3119
- With this one, there is: ef4429a

Except an oblivion, I see only two commits between these two nightlies, which seem - the first or second ? - to be the triggers of this fatal outcome.
Ie: - https://github.com/musescore/MuseScore/commit/ef4429accf37fc3d6abfd1c1d…, and
- https://github.com/musescore/MuseScore/commit/858ddb25e8d3da6cc59bbc4c9…

EDIT: in another way, I see this also (but probably not related at all?) : https://github.com/musescore/MuseScore/commit/a9cec566a40704a425f649fcd…

Title Crash by changing time signature in a measure in Continuous view when a glissando extends from the previous mesure Crash by changing time signature in a measure in Continuous view when a glissando extends from the previous measure