Crash corrupted Musescore file
Musescore version: 2.0.3, Revision 3c7a69d
I have an issue with my laptop that sometimes when I unplug the headphones from the USB port, the machine crashes. (I haven't been able to figure out how to fix that problem, short of retiring those headphones, to which the problem seems to be specific, which so far I haven't been motivated to do.)
In any event, I needed to unplug, so made sure I saved my Musescore file before unplugging the phones. I did not close Musescore.
Sure enough, the machine crashed. When I restarted, re-launched Musescore and attempted to re-open the file, Musescore said it couldn't open it. (I didn't write down the actual message -- sorry -- and can't get it back now, as I've replaced the file; but it was clear that it was a file corruption issue.)
I can't recall a crash causing a file in any other program I use to get corrupted. Obviously one would expect to lose unsaved changes - but not to have the saved version of a file become unusable.
Is this a known issue?
Many thanks.
Comments
When MuseScore attempted to recover your score, it worked from an special hidden file that indeed would be known to possibly be bad if the machine died while writing it - that shouldn't be surprising. But that is totally separate from the actual score you saved - that version should still be perfectly fine. Only the auto-saved version that MuseScore uses to recover your file from would potentially be corrupted by a crash that happens while writing that file.
In reply to When MuseScore attempted to by Marc Sabatella
The machine didn't crash while writing the file. It crashed well after that operation had been completed. Also, I didn't use an auto-recovered file: I attempted explicitly to load the file on the disk.
In reply to The machine didn't crash by manonash
I meant, the crash probably occured while it was writing the auto-save.
Anyhow, sorry, I misinterpreted your previous comment to imply you tried recovering from that.
If your file is corrupted, it could be because the crash occured before your disk cache finished clearing, if you didn't explicitly turn off disk caching. Because indeed, there is no way a system crash after the save finished would affect MuseScore itself in any way, and no way MuseScore would be touching your file after the save.
It's also possible there is no write failure, just a siple score corruption unrelated to the system crash. If you see a message offering to tell you details but giving you the option to ignore, that's what is happening. See https://musescore.org/en/node/54721 for info on fixing corruptions.
If that doesn't help, please post the score you are having problems with so we can understand the situation better.
In reply to I meant, the crash probably by Marc Sabatella
Is the disk caching facility to which you refer associated with Windows rather than Musescore? If so, where is it turned on and off?
Regrettably, I overwrote the corrupted file with a copy that wasn't too far behind it. I'll be sure to hand on to it next time.
Thanks.
In reply to Is the disk caching facility by manonash
Disk caching is indeed handled by your operating system, and/or the device driver for your disk. You need to consult the appropriate documentation you learn how to turn it off for your particular configuration. I assume somewhere you can right click on an icon for your drive and see options in a Properties dialog.