2025-11-24 13:37:53.0785|INFO|LauncherBackend.Services.ThriveRunner|Thrive detected as properly started
2025-11-24 14:00:39.1819|INFO|LauncherBackend.Services.ThriveRunner|Thrive process exited with code: 139, total runtime: 00:23:22.3649631
2025-11-24 14:00:39.1835|INFO|LauncherBackend.Services.LauncherPaths|Expected Thrive user data folder to be: /home/david/.var/app/com.revolutionarygamesstudio.ThriveLauncher/data/Thrive
2025-11-24 14:00:39.1848|WARN|LauncherBackend.Services.ThriveRunner|Thrive didn't run successfully (crashed or another problem occurred)
2025-11-24 14:00:39.1848|INFO|LauncherBackend.Services.ThriveRunner|Thrive exited non-successfully but no crash dumps exist
2025-11-24 14:00:39.6869|INFO|ThriveLauncher.ViewModels.MainWindowViewModel|Showing the launcher again after running Thrive
2025-11-24 14:01:06.7463|INFO|ThriveLauncher.ViewModels.MainWindowViewModel|User requested cancel of current playing of Thrive
2025-11-24 14:01:06.7468|INFO|ThriveLauncher.ViewModels.MainWindowViewModel|Closing play popup due to cancellation
2025-11-24 14:01:06.7480|WARN|ThriveLauncher.ViewModels.MainWindowViewModel|Ignoring runner message as not currently playing
2025-11-24 14:01:06.7480|WARN|ThriveLauncher.ViewModels.MainWindowViewModel|Ignoring runner output message as not currently playing
I already closed it, is it saved somewhere? But there didn’t seem to be anything there either. You can see in the launcher logs that the dump was not detected. I can say that this happened when exiting the editor.
3 Likes
aah31415
(The maker of SitF, Radiostrocity, The Lifenote and TGBing; The Second Ascended...; And just maybe a security warning come alive...?)
4
If you don’t have the log, even in the log files, could you provide us with a save that consistently gets this crash or a reproduction method to achieve it?
The game keeps the last few log files in the Thrive logs folder. There’s a button in the Thrive options to open the folder.
Ever since we updated to Godot 4 the crash dumps tool has been not reimplemented. However in most situations the game logs actually do have indications on what went wrong if a crash happens.
It seems that’s not the right log file? At the end it says that the game is closing due to the “quit” button being pressed, so unless it crashed on shutdown, that’s not the relevant log file for this situation.
aah31415
(The maker of SitF, Radiostrocity, The Lifenote and TGBing; The Second Ascended...; And just maybe a security warning come alive...?)
11
This seems to be the broadphase collision thing again. Pretty sure we already know the cause of this glitch, though thanks for your help anyways AsfhtgkDavid!
Hopefully we do. If it is that division animation physics thing, then yes it is fixed. But as it seems somewhat rare to trigger we likely won’t have enough testing resources to confirm that until after all the players get the 0.9.1.1 patch in their hands.