SEGFAULT trying to switch visible state of Bracket with "V" key

• Mar 18, 2017 - 09:36
Reported version
3.0
Type
Functional
Severity
S2 - Critical
Status
closed
Project

Testing the "V" shortcut to switch the bracket visible state(the state doesn't get changed, the bracket only gets deselected), there happens to be a SEGFAULT. The steps to recreate the issue :

1. Create a new Score (for ex. using GrandStaff template).
2. Select the bracket then press "V" key, it should get deselected. Do Selecting and pressing V one time. (If no bracket used in Score, add it from the brackets palette under the advanced workspace and try the same aforementioned steps)

The Application should crash.


Comments

Here is stack trace for reference:

1 main_arena 0x7fffeb8d4c28
2 Ms::ScoreElement::isNote scoreElement.h 314 0xb3e075
3 Ms::MuseScore::endCmd musescore.cpp 4594 0xcce0dc
4 Ms::Score::endCmd cmd.cpp 190 0x149eebc
5 Ms::ScoreView::cmd scoreview.cpp 3131 0xb2c39e
6 Ms::MuseScore::cmd musescore.cpp 5015 0xcd0625
7 Ms::MuseScore::cmd musescore.cpp 4565 0xccddfe
8 Ms::MuseScore::qt_static_metacall moc_musescore_IKSZSQWDH4YDZS.cpp 740 0x114c433
9 QMetaObject::activate(QObject *, int, int, void * *) 0x7fffec12cd49
10 Ms::ScoreTab::actionTriggered moc_scoretab_QR4BWIRYNXAVBM.cpp 184 0x115391d
11 Ms::ScoreTab::qt_static_metacall moc_scoretab_QR4BWIRYNXAVBM.cpp 97 0x1153591
12 QMetaObject::activate(QObject *, int, int, void * *) 0x7fffec12cd49
13 QActionGroup::triggered(QAction *) 0x7ffff3c1c4ff
14 ?? 0x7ffff3c1d079
15 QMetaObject::activate(QObject *, int, int, void * *) 0x7fffec12cd49
16 QAction::triggered(bool) 0x7ffff3c18c92
17 QAction::activate(QAction::ActionEvent) 0x7ffff3c1b3f0
18 QAction::event(QEvent *) 0x7ffff3c1bd6c
19 QApplicationPrivate::notify_helper(QObject *, QEvent *) 0x7ffff3c1f34c
20 QApplication::notify(QObject *, QEvent *) 0x7ffff3c26b61
...

In MuseScore::endCmd(), the address for e is 0x7ffffffff9ad8, which looks suspicious, but seems to be valid...I don't know....

Note, it seems if I have a grand staff piano with another single-staff instrumnet, that this crash doesn't occur. But it does occur when the grand staff is alone.

Also I'm noticing a lot of cmd() calls