Jump to content

Fatal(ity) Crash - Silent. No black hole. Snippy madness averted.


JRup
  • Branch: Live Branch Version: Linux Pending

Game will load save file up to almost paused state show where last was saved and then crash, silently. No black hole.

Game was playing just fine until that point today. This is not the first time this has happened, however. It started to happen recently, after the most recent slew of updates (post-CVE update) and I've been searching for clues on how to reproduce without much success. 

I've proceeded to destroy each and every one of the slimelung infested tile that present germ proliferation/decay just to make sure there was no mathing that's not mathing occurrence.

I've had some anecdotal success in not having the issue appear when performing manual saves when dupes are just done with their bathroom duties or aren't using them at the time.

Last actions taken in game today were mining bleachstone and sweeping it. Auto save proceeded just fine and some time after a manual save was performed.

Both latest autosave and the manual save show the reported issue.

I can see that at the end of the log file we get some fun stuff.

image.png.b7fe04aa29bff875578279e06139101e.png

Removing mods has no bearing in the crashyness once the save file has the problem. Once this happens then many autosaves from an extended play session (approx 7 or 8 autosaves) may present the issue.

In this event I've loaded the autosave prior to this one and it works properly.

Both will be uploaded to the report.

Cycle 18033 has issue.

Cycle 18032 loads proper.

image.png.f830116dbbfaa9a617c5f4d9091296a5.png

On a different occasion: I've managed to load the defective save file after loading a prior working version. But this is at best anecdotal and may be attributed to chance.

I'll proceed to load the working save file and continue playing from there.

Still on Ubuntu 18.04, btw.


Steps to Reproduce

Attempt to load "DeCrew 536a Cycle 18033.sav"

Wait until load process finishes.

Expected:

  • Game enters ready state (paused) and waits user input.

Observed:

  • Game crashes silently. It may show loaded save up to ready state and final checks will signal termination after about 1 second.

DeCrew 536a Cycle 18033.sav DeCrew 536a Cycle 18032.sav




User Feedback


Minor update, had this happen this morning from waking up the computer (from suspend).

Launched a save file that was confirmed working and it crashed.

Restarted and launched the same save file. It now works. I shall assume OS shenanigans and will monitor further.

I will leave this here for reference.

  • Sad Dupe 1

Share this comment


Link to comment
Share on other sites

Hello! Solution to crash (first one) provided. But first more context.

I've been able to continue playing with some save files loading and some not. With an increasing amount of them not loading. But stubbornness has paid off and I now have results to present.

I first checked context for "funlockfile" & ubuntu to find out whether there was something out of date that could be fixed (besides the crusty old 18.04)

No luck there.

Then I searched "DiseaseEmitter Oxygen not included" third page presents us with this little jewel:

[beta] Silent game crash caused by germ-related issue

This is from one of the save files generated prior to having found the solution, notice something here?

image.png.8077ff7b3eed4a5a198f7cadfe9a4147.png

Sanishells may not like the updated ONI when surrounded by germs? Who knew?

 

The aforementioned article bug report suggested issues for when sanishells are doing their voodoo and a very suspiciously silent crash, so I then proceeded to relocate the offending critters to a germ-free area. The current state of the save does not require sanishell-powered disinfection so no problem with having them elsewhere...

The second crash (logfile added later) may be due to playing for too long, make sure to take breaks or the OS will do it for you.

I've been able to load manual and autosave files since the sanishell relocation. Don't worry, they're happy.

With that I can report that the issues plaguing my save file are gone.

Cheers!

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...