Jump to content

Player.log spammed with line "[1] [WARNING] Couldn't emit CO2" causes log to fill and client to crash


amfournda
  • Branch: Live Branch Version: Linux Fixed

The attached save file causes my Player.log file to be filled with the message:

[21:41:37.658] [1] [WARNING] Couldn't emit CO2

thousands of times a second. This causes the log file to fill rapidly, to the point where it reaches roughly 3/4 of a gigabyte in size before the game crashes. It's unclear what object is attempting to emit CO2 and failing, but some form of log rate limiting might help this sorts of issue. Interestingly upon the game crashing, if I use Steam to validate the game files it claims one file fails to validate and redownloads it. From the Steam content log:

[2020-12-27 16:26:40] AppID 457140 update changed : Running,Validating,
[2020-12-27 16:26:40] Validation: corrupt chunk faa42b2161d93cfea87ac8789a5d4b8c3ac81d63 has 59be0d3f47a88c0749aed16a1aae65c444bfcb62 at offset 0 (11 bytes)
[2020-12-27 16:26:40] Validation: 1 chunks corrupt of 1 total in file "OxygenNotIncluded_Data\MonoBleedingEdge\etc\mono\registry\last-btime"
[2020-12-27 16:26:46] Validation: full scan in "/home/erin/.local/share/Steam/steamapps/common/OxygenNotIncluded" found 1/864 mismatching files (11 bytes/1.98 GB) in 5 seconds).
[2020-12-27 16:26:46] AppID 457140 state changed : Fully Installed,Update Queued,Files Missing,Update Running,

Validation confirms the files are good if run a second time, and after restarting the game it will run fine for an amount of time until the log file hits that 3/4 of a gigabyte in size again and crashes.

 

Thank you for making a wonderful game and supporting it on Linux. I really enjoy it and hope this bug isn't too hard to squish.

Lunar Committee.sav


Steps to Reproduce
  1. Load attached save file
  2. Unpause game
  3. tail Player.log file to see logspam
  4. Play for an hour or two for log to become extremely large (about 3/4 of a Gig on my machine) and game will crash



User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

Changed Status to Fixed

This is caused when a duplicant breathes in space with an oxygen mask. I've removed the debug log in development and it will go out in the next update. Thanks for the report.

  • Like 1
  • Thanks 1

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...