Moho crashes while undo - Cause and Solution
Posted: Tue Apr 19, 2022 11:39 pm
I had the feeling that the crashes while undoing that people are reporting were related to Moho's autosave feature, so I decided to test that hypothesis.
The tests consisted on making a lot of diverse things like copy pasting keyframes, changing shape colors, moving points, creating shapes, moving all kind of bones, etc, and then undo and redo all those changes to see if Moho crashes. I ran 10 test in total: 5 with autosave on and 5 with autosave off. This was done with Moho 13.5.3 on Windows 10.
Each of the 5 "autosave on" tests ended in a crash, and not only that, but all of them with errors while tryin to recover the autosaved file (the classic "unable to parse from jason" or something similar).
I wasn't able to reproduce these crashes on any of the 5 "autosave off" test I ran. I hope this is not just a stupid coincidence (it happens) and my conclusion is that the autosave feature is buggy as it was in the past and all users should disable it. At least you should try it to see if it works for you. You can disable it at Edit - Settings - Documents.
You can find some nice scripts to make autosaving or incremental savings from the generous synthsin75 and davoodice2 using this forum's search bar.
Note for the devs: I thought that maybe some particular action was linked to the crashes, like breaking a shape deleting one of its points or something strange like that, so I ran the test only moving existing points with the magnet tool and then undoing but it crashed anyway, so it's probably not related to a particular action but it looks like any action will eventually cause a crash if you keep undoing them with autosave on.
Update: Moho's team released a new version today (13.5.4) that fixes this bug among others. I have updated to this new version and repeated the tests. After 6 minutes of stress testing the undo-redo system with autosave activated and styles used I wasn't able to crash the program. I'm too bored to continue.
Congratulations!
The tests consisted on making a lot of diverse things like copy pasting keyframes, changing shape colors, moving points, creating shapes, moving all kind of bones, etc, and then undo and redo all those changes to see if Moho crashes. I ran 10 test in total: 5 with autosave on and 5 with autosave off. This was done with Moho 13.5.3 on Windows 10.
Each of the 5 "autosave on" tests ended in a crash, and not only that, but all of them with errors while tryin to recover the autosaved file (the classic "unable to parse from jason" or something similar).
I wasn't able to reproduce these crashes on any of the 5 "autosave off" test I ran. I hope this is not just a stupid coincidence (it happens) and my conclusion is that the autosave feature is buggy as it was in the past and all users should disable it. At least you should try it to see if it works for you. You can disable it at Edit - Settings - Documents.
You can find some nice scripts to make autosaving or incremental savings from the generous synthsin75 and davoodice2 using this forum's search bar.
Note for the devs: I thought that maybe some particular action was linked to the crashes, like breaking a shape deleting one of its points or something strange like that, so I ran the test only moving existing points with the magnet tool and then undoing but it crashed anyway, so it's probably not related to a particular action but it looks like any action will eventually cause a crash if you keep undoing them with autosave on.
Update: Moho's team released a new version today (13.5.4) that fixes this bug among others. I have updated to this new version and repeated the tests. After 6 minutes of stress testing the undo-redo system with autosave activated and styles used I wasn't able to crash the program. I'm too bored to continue.
Congratulations!