Crash on inspector parameter change when tie and slur selected

• Apr 29, 2020 - 17:10
Reported version
3.4
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
won't fix
Regression
Yes
Workaround
Yes
Project
MuseScore

Simplest way to reproduce the failure:
1) Create four notes of same pitch
2) Set a tie between the first and the second note
3) Set a slur between the third and the fourth note
4) Select the tie and the slur
5) Open the inspector and try to change a parameter -> Crash

Used OS is Windows 10. The failure appears on version 3.4.2 as well on the last nightly build.
Although it's clear that ties and slurs are different kind of things that should not be treated in the same way, this sometimes unintended combination of selected objects shouldn't lead to a crash.

Comments

• Apr 29, 2020 - 19:56
Regression No ⇒ Yes

Works in 2.3.2, so a regression against at least that
Edit: works in 3.1.0 and 3.2.3 too!
Crashes in 3.4.1, 3.4.2 and the latest development code though

Reply

• Jul 12, 2021 - 06:20

I reproduced this too but I could only do so if I first forced the slur to direction "Up" and the tie to direction "Down", then selecting both, and trying to adjust the direction via the inspector - just opening the dropdown crashed.
But the inspector is completely rewritten in v4.0 so unlikely to be an issue there (actually it's not implemented for slurs & ties yet)

Reply