I've been getting occasional crashes after career levels in the Linux client. Is there a log file that I can peruse and/or share in order to narrow down the cause?
On Windows, Godot prints errors like that to the console window. I can view the console window if I launch a command line and run the game from there
$ ./turbofat-win-v0.7000.exe Godot Engine v3.5.2.stable.official.170ba337a - https://godotengine.org OpenGL ES 3.0 Renderer: NVIDIA GeForce GTX 970/PCIe/SSE2 Async. shader compilation: OFF WARNING: Unrecognized save data version: '512b' at: call (modules/gdscript/gdscript_functions.cpp:789) WARNING: Unrecognized save data version: '512b' at: call (modules/gdscript/gdscript_functions.cpp:789) WARNING: Unrecognized save data version: '512b' at: call (modules/gdscript/gdscript_functions.cpp:789) WARNING: ObjectDB instances leaked at exit (run with --verbose for details). at: cleanup (core/object.cpp:2070) ERROR: Resources still in use at exit (run with --verbose for details). at: clear (core/resource.cpp:417)Does that work on Linux too?
It does. I got the following output from running the game in the terminal until I was able to reproduce a crash:
Godot Engine v3.5.3.stable.official.6c814135b - https://godotengine.org
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
OpenGL ES 3.0 Renderer: VEGA10 (radeonsi, vega10, LLVM 15.0.7, DRM 3.42, 5.15.0-92-generic)
Async. shader compilation: OFF
corrupted size vs. prev_size in fastbins
[1] 1789513 IOT instruction (core dumped) ./turbofat-linux-v0.8101.x86_64
The program's returned error value was 4. The game ran for some period of time after the async line, and the crash happened after the fastbins line (though I can't say how long the fastbins line had been present before the crash).
I see. Doing some googling, it seems like it's this godot bug:
https://github.com/godotengine/godot/pull/74566
I haven't seen this so maybe it's Linux-specific or only affects certain graphics cards. There's no workaround, so unfortunately I think fixing it would require someone smarter than me fixing the game engine, or porting this fix over to 3.5.x. Thanks for the report, I wish I could do more to help!