This actually means the game froze. An actual crash is handled by the crash handling mechanism, but if it freezes, the UI just detects that no response is coming from the game engine.
Yep, I see that it's a freeze and not a crash, though when the disk I/O settles down the engine/UI doesn't resume.
Oof. I see. This is most likely due to the game saving a screenshot of the whole screen with every savegame. This probably also means that playing in a higher resolutions takes more time and space for the savegames since the saved preview is probably also larger.
I've reported this odd disk space usage issue internally already; it makes no sense for a huge image to be saved for a tiny thumbnail in the UI. Not to mention, it overloads the available cloud sync space when quick saving often.
That would explain why auto-saving takes a noticeable delay. (It tends to be pretty seamless in most games.)
I'm playing at 1440p, that'd be considerably big to PNG. Particularly in a game like this with FREQUENT auto-saves. 🙂
Thanks for mentioning it upstream.
