Quitting after a long day no longer crashes the engine

After about seven hours of use, Bandicot's engine crashed as it was closing. The history keeper, the part that saves versions of your files, checks every so often whether a session is running, and the engine was tearing that list down at the same moment.

The engine now stops the history keeper before it takes the list of running sessions apart, so the two can never meet. The longer Bandicot had been running, the bigger the list and the wider the gap, which is why it only showed after a long day.

Crashes you can read

Every new build now keeps its symbols in a private folder next to your logs, one folder per build for the newest twenty, without making the app any bigger. If something does crash again, the report can be matched to the exact line of code that failed.