MuseScore crash and weird behaviour on deleting 4 staves

• Oct 23, 2009 - 23:45
S2 - Critical

The following photos are taken in the exact order of the file names. I first selected a row that I wanted to delete, then deleted it, then tried ctrl-z and the weird stuff started happening. It gets even weirder with the other example for which I didn't provide the first 3 steps because they are so easy. I am running Nightly 2244 on Windows 7 RC 32-bit. Please if you can guys, fix this because it is kind of annoying. MuseScore seems to handle smaller numbers of measures with 4 staves pretty well, but when the numbers grow, it causes this ugly GUI glitch, and, if you try to delete those visual artifacts that are left over, MuseScore will crash, or, a sure way to crash it is to redo after you tried undo with ctrl-z in order to undo the deletion. That will crash MuseScore for sure alongside the following error messages:

Microsoft Visual C++ Runtime Library

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


Problem signature:
Problem Event Name: APPCRASH
Application Name: nightly.exe
Application Version:
Application Timestamp: 4adfa2bb
Fault Module Name: nightly.exe
Fault Module Version:
Fault Module Timestamp: 4adfa2bb
Exception Code: 40000015
Exception Offset: 00108071
OS Version: 6.1.7100.
Locale ID: 1048
Additional Information 1: 67b5
Additional Information 2: 67b58c24656bc42f88be5a419f332a6f
Additional Information 3: cd7a
Additional Information 4: cd7afa7d172b9817400bd02171f8b524

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:

Attachment Size
1.png 328.12 KB
2.png 326.28 KB
3.png 326.28 KB
4.png 359.85 KB


The best way to increase the chances of a bug getting fix is to make it really easy to reproduce. I tried deleteing and undoing with my own scores but couldn't reproduce the problem. See if you can create a simple example and attach the actual MuseScore file you are working with. Better yet create a smaller MuseScore file that shows the problem in its simplest form.

sorry man, my mistake was that I had uploaded in the place of screenshot number 3 the same as number two......... picture number 3 was supposed to look something like number 4 but on the same zoom and system........
what's even more crazy is that I have deleted the screenshots from my laptop after I did the thing, and, now even I can't redo the scenario and make the score look weird again...................... this is crazy............
I imported the same midi file on nightly 2244 and tried the same thing but it just won't work..........
Maybe I also did something else before I tried deleting those measures like adding less stretch or something that made it look that weird.........................

Sorry for the clutter but one thing is for sure, the crash DID occur.............

Maybe there was something wrong with the score?