Open Chilaila opened 3 months ago
Seems like it is reproducible without shortening the measure
https://github.com/musescore/MuseScore/assets/69917893/72abc5d0-59e6-4804-ae7d-e3fdc577adf5
I reproduced this once in master, but on restart was no longer able to reproduce. So it seems this one is potentially quite inconsistent.
Issue type
Crash or freeze
Bug description
Muse Score Studio crashes on the following method:
** Update, step one unnecessary to crash program 1 Shorten any measure 2 Add on the next measure two Staff Type Changes (Done by error so two layered on top of each other) 3 Delete both Staff Type Changes. 4 Muse Score Studio crashes with no errors, just closes the app.
System Information: OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630831, revision: 22b46f2
Steps to reproduce
1 Shorten any measure 2 Add on the next measure two Staff Type Changes so it's layered on top of each other. 3 Delete both Staff Type Changes. 4 Muse Score Studio crashes with no errors, just closes the app.
Screenshots/Screen recordings
https://github.com/musescore/MuseScore/assets/15065835/c78b3065-034a-4a2d-9f76-514ae26a66d9
MuseScore Version
MuseScore Studio version (64-bit): 4.3.2-241630831, revision: [22b46f2]
Regression
No
Operating system
Windows 11
Additional context
It seems that it's not happening on all machines. The one in question is a laptop with two build-in graphics cards, that might be the problem.
Lenovo DxDiag.txt