Frequent crashes with Musescore 3.2.3 d2d863f
Reported version
3.2
Type
Performance
Frequency
Once
Severity
S3 - Major
Reproducibility
Randomly
Status
needs info
Regression
No
Workaround
No
Project
Loved Musescore on my earlier version of Ubuntu, but I'm getting frequent random crashes since moving to Bionic Beaver and the latest version of Musescore. (3.2.3) One was severe enough to corrupt the file and render it unopenable. (Funk file attached) Running a 8 gig ram mid teens vintage Dell Latitude (2015 or so.) No clear pattern to crashes -- can happen during cut and paste, playback or manual note entry. Love to get to the bottom of it -- any debugging suggetions? Thanks! Al
| Attachment | Size |
|---|---|
| Funk.mscz | 0 bytes |
Comments
Your file has nothing in it so you will need to look for a backup. See https://musescore.org/en/node/52116. Also, the latest version is 3.3.3, I'm not sure about the rules for upgrading with your version of Linux.
In an case, in order to investigate a crash or other issue, we would need precise steps to reproduce the problem.
In reply to In an case, in order to… by Marc Sabatella
Since the crashes happen randomly, the only specific steps I have to offer is open the program, do some work on a song, curse when it crashes about 10 to 15 mins in. Hard reboot. Rinse and repeat.
In reply to Your file has nothing in it… by mike320
For whatever reason, no backup exists. I’ll see if 3.3 will load up and fix issue. Thanks!
Backups are always created in two situations.
You open a score the save it and musescore creates a .filename.mscx, file (starts with . and ends with , that is made invisible) in the same folder as the original score. You must find this file and delete it or it is still there. Nothing will do this automatically.
If you suffer a crash and have auto save turned on, as long as the session lasted long enough for auto save (2 minutes by default) there will be a file called SCxxx.mscz where xxx is a random group of letters and numbers created for every file open. When you restart MuseScore after a crash telling MuseScore you do not want to restore the session will cause MuseScore to delete the SCxxx.mscz file otherwise the file is still there and visible.
If you don't have a backup, then none of the scenarios I describe here are true.