MuseScore 3.4 crashes when quitting
Hello,
I was happy to install version 3.4.... until I tried it. It seems to work correctly, as long as I don't try to update language packages (it fails – always). However, it seems to crash semi-randomly AND it crashes each time I quit.
I did have time to see that version 3.4 uses the decimal marker I use on my system (i.e. the comma) rather than the U.S. decimal point.
Anyway, I decided to remove and reinstall version 3.3.3 which seems rock solid on my system.
System info:
Windows 10, French-canadian (numbers are configured with the comma as decimal separator and space as thousands separator)
Comments
I haven't seen any crashes on exit, nor has anyone else reported such a thing, so I suspect the problem has to do with the score you were editing at the time, or something else specific to your particular environment. Can you attach a score and give precise steps to reproduce the problem? Literally just start MuseScore, open the score, then close MuseScore?
Why falling back to 3.3.3 rather than 3.3.4?
Maybe #300107: Version 3.4 is likely to crash if no score is loaded?
In reply to Maybe #300107: Version 3.4… by Jojo-Schmitz
Sounds exactly like that.
Now that I think of it, the radom occasional crashes were when no files were open and I was looking at menus. During that time, I also tried to update language files and I always got an error... until it crashed.
The "crash when quitting" is 100% reproducible. When I click on the close box (top right of the window on Windows, the song(s) close, then the program appear to quit normally. And it does, except I see the Command window and the crash report dialogue afterwards telling me Musescore has crashed, do I want to send a report?
So strictly speaking, when it crashes, there aren't any scores loaded anymore.
Finally, why did I reinstall 3.3.3? I had the install file on hand.
Thanks
In reply to Sounds exactly like that… by mgagnonlv
I see. 3.4.1 is out now and has it fixed, so you can update again ;-)
In reply to I see. 3.4.12 is out now and… by Jojo-Schmitz
Thanks for the support.
I just reinstalled it and I can confirm it has been fixed.