selecting master palette leads to crash
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S1 - Blocker
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
OS: openSUSE Leap 15.0, Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 1edd676
Steps to reproduce:
- Start MuseScore
- select view->master palette
->crash
Comments
I cannot reproduce here with: OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 1edd676 (as usual, release build)
Could you revert to factory settings, and check again ?
crashes for me too, actually an assertion failes, so this (probably) isn't seen in the nightlies:
Fatal: ASSERT: "!empty()" in file ...\MuseScore\libmscore\stafftypelist.cpp, line 44 (...\MuseScore\libmscore\stafftypelist.cpp:44, )
only for self-built versions apparently
@cadiz: The crash still occurs after a revert to factory settings or rebooting the system.
As mentioned in another issue entry, I didn't have checked all nightlies of the last days, but there's no crash for example with 3fdfab3
@kuwitt: crashes for you on a self-built? Or on a development build?
I'm always using the developments builds so far of: https://musescore.org/en/download#Development-builds
The crash occurs with 1edd676, but not with the previous available development build 9e94cec
Fixed in branch master, commit adf7727a38
fix #277952 selecting master palette leads to crash
Automatically closed -- issue fixed for 2 weeks with no activity.