v0.5.5 was released on August 19, 2026. It is aimed at crash clarity and display failures: it makes the cause of a crash easier to read and replaces media that was triggering GPU and capture-hook problems.
When a crash or display failure hits, this order keeps the evidence intact before you change settings.
Make sure you are on v0.5.5 or later before diagnosing a known issue.
Record the save, the action, and the display state so the failure is repeatable.
Keep the log file. Crashpad stays opt-in unless the developer asks for it.
v0.5.5 does not change the core factory loop. It makes failures easier to read and removes media-based crash triggers that interrupted longer sessions.
v0.5.5 focused on making crashes easier to diagnose and removing a few display-related failure points, not on changing production systems.
Some crashes can still be hardware-specific or version-specific, so keep the log evidence and confirm the exact build before assuming the patch covers your case.
The update highlights clearer diagnostic logging, media-related crash reductions, Alt+Enter fullscreen support, and a temporary macOS right-click workaround.
Confirm the version, reproduce once, and preserve the relevant log evidence before escalating.