Crash following undo+octave up
Reported version
4.0
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
Crash while notating
1: Input two notes
2: undo once, removing the second note
3: Ctrl+Up, to octave up first note
4: crash
edit:
crashes regardless of ctrl or not, also crashes with undo+down
Comments
update: both undo+up/down. regardless of octave or half step
I am not able to reproduce this in 4.0.0 (on a single flute staff), and I've tried every combination of notes, undoes and octaves up/down.
Edit: This test was performed on Windows 10.
In reply to I am not able to reproduce… by Trainzack
tried single staff with same issue, however i tested two other computers and indeed wasn't able to reproduce there.
Machine with issue:
- Win11_22000.1219, mid-range laptop
Machines w/out issue:
- Win10_build_19045, high end desktop
- Win10_build_19042, low-end laptop
Doesnt seem performance related
Possibly OS related but not conclusive
I have independently encountered this bug on a Windows 10 laptop, and can consistently reproduce it on both stable 4.0 and in the latest (002fd32) nightly. I create a new score using the ”General->Treble Clef” template, enter two quarter notes, undo once, half-step or octave up or down, observe the crash.
Windows Event Viewer says, for the stable version:
Faulting application name: MuseScore4.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2364, time stamp: 0x5b7d4d22
Exception code: 0xe06d7363
Fault offset: 0x000000000002cd29
Faulting process id: 0x3398
Faulting application start time: 0x01d91a3f1a210030
Faulting application path: C:\Program Files\MuseScore 4\bin\MuseScore4.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 2610e497-452c-4531-b861-c58b73733b68
Faulting package full name:
Faulting package-relative application ID:
I am encountering this issue also in a bassoon part.
I'm consistently getting this on the latest release (updated yesterday). I've only tested with the voice instrument, but can confirm that it also happens in a blank file. To reproduce simply enter two notes, then hit ctrl+Z followed by ctrl+up.
Below is copied from the about window in MS, but I'm actually on Windows 11. This would confirm what toidinami mentioned about this crash possibly being related to OS version.
OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230651553, revision: dbe7c6d
four is still few
Best report this on GitHub
In reply to four is still few Best… by Jojo-Schmitz
Ah, that's what frequency means! I was a bit confused by seeing both that and reproducibility. Sorry for the confusion!