crash bug in MuseScore 2.0.2 revision f51dc11

• Jun 6, 2016 - 23:23

I was running MuseScore Portable 2.0.2 on Windows Vista Home Premium Service Pack 2 (32 bit), on a very old laptop with an Intel T2060 with 2 GB of memory. I didn't have a lot running on the machine (a PDF viewer, Bing Desktop, and Windows Explorer. I didn't even have a browser running.

However, I was transcribing a large score (about 18 staves, 485 measures, 144 kB mscz so far), and I have been getting low memory warnings from Windows from time to time.

The error message was something along the lines of "The C runtime library has encountered an unexpected [maybe unhandled] error and must be shut down." I clicked on the dialog box "OK" button (neglecting to copy down the exact error message) and MuseScore went away.

My best guess is that some memory allocation is failing, and the exception handler chain doesn't know how to fail gracefully.

When I started again it offered to resume from the auto-save file, I said yes, and it said that the auto-save file was corrupted. (Fortunately, I save manually fairly often.)

This could be counted as two bug reports (the crash and the corrupt auto-save file), but this is only meant to report the crash. I will file a separate auto-save bug if I can find the auto-save file.


In order to help, we would generally need you to attach the specific score you are having problems with and precise step by step instructions to reproduce the problem.

There wetre quite a few crashes fixed betwene 2.0.2 and 2.0.3, also a fix involving a case where the auto-save file could be corrupted. Very possibly both problems you are seeing have already been fixed, so you should definitely update. On the other hand, if you are working on such a large score that you are running low on memory, it's possible you actualy ran *out*, and that will probably crash mone way or another. Better to break the score up into separate pieces.

Do you still have an unanswered question? Please log in first to post your question.