Crash when removing added time signature if subsequent tie and rest in next measure

• Dec 7, 2018 - 04:34
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

macOS Delete of time signature in any piece file size 70k or larger and the crash is very repeatable.

Attachment Size
Crash-TimeSig-Delete.txt 81.27 KB

Comments

• Dec 7, 2018 - 04:49
Severity S1 - Blocker ⇒ S2 - Critical
Status active ⇒ needs info
Type Graphical (UI) ⇒ Functional

In order to investigate, we need an actual score and precise steps to reproduce the problem.

Reply

• Dec 8, 2018 - 12:26
Frequency Few ⇒ Many
Reproducibility Randomly ⇒ Always

Hi Marc

The crash is repeatable on macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.0.0., revision: e96bb9119b1b05bc1376d8f623c29410cef9a427. (Beta 2).

Method to cause the crash

Add additional time score anywhere on the score. saving or not has no effect. also happens opening up a file fresh with an additional time signature in it already.
to cause the crash .... Delete the time signature on the score.

Interestingly in looking for a file to demonstrate the crash the demo file all dudes included the beta causes the app to crash on attempting to open it!

Attachment Size
Killing_Me_Softly_With_His_Song-3 copy.mscz 35.57 KB

Reply

• Dec 8, 2018 - 13:36
Title Delete 6/4 time signature causes beta and nightly macOS 33a1dae to crash ⇒ Crash when removing added time signature if subsequent tie and rest in next measure
Frequency Many ⇒ Once

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4346, revision: a9203cb

Test file: test2.mscz

See:

Video_2018-12-08_142728.gif

Reply

• Dec 8, 2018 - 15:04
Priority ⇒ P0 - Critical

Confirmed. As shown above, 4/4 score, add whole note, add 3/4 time sig in front thus changing it to dotted half tied to quarter, now remove the time sig. We end up calling qFatal() in checkRest(), range.cpp, so set your breakpoint there if you want to start debugging this...

Reply