Jump to content

Getting random hangs in ONI


Uncrushed
  • Branch: Live Branch Version: Linux Pending

Thank you for making games that work Flatpak on Linux!!!  I've played over 1K hrs of DST that way and can't think of a single hang in that time.  I've played ONI for 14 hours so far and have gotten 3 hangs.  I'm using Steam in Flatpak on Ubuntu Linux 22.04 LTS (with snap removed).  This is the first hang that I documented.

Please note that Flatpak gives apps very limited access to the host OS or filesystem, so I found log file in:

~/.var/app/com.valvesoftware.Steam/.config/unity3d/Klei/Oxygen Not Included/Player.log

I used these 2 commands to find it:
$ cd ~/.var/app/com.valvesoftware.Steam/
$ find . -type f -name *.log -mtime -1


Steps to Reproduce

The first time I got this issue (around 16:45), I was doing something:

  1. Open "Vitals" from the top-nav
  2. Single-clicked on a character's name
  3. Hang

Screenshot from 2023-06-21 16-44-12.png

The next time (18:00), I was just scrolling around.  Maybe something completed?  IDK.  I'm attaching another log file, but the ending looks the same.  If this is truly a Flatpak related issue, then I might need to give Steam permission to do something that it didn't need to do for DST.

 

ONI_player_log_2023-06-21_18-00.log




User Feedback


I ran the Steam flatpak from the command line to see if I could get any other info, but it didn't crash for 3+ hours.  Maybe that's my workaround?

Share this comment


Link to comment
Share on other sites

Here are some screenshots of the System Monitor, 2 while running fine, 2 after the crash.  The 2 after the crash are identical, except that one is full-screen showing what was maybe happening at the time of the crash in the game.

Let me know if there's more I could do to help diagnose this.  I can't think of anything else to try ATM.

Screenshot from 2023-06-23 09-58-20.png

Screenshot from 2023-06-23 10-13-21.png

Screenshot from 2023-06-23 15-15-46.png

Screenshot from 2023-06-23 15-15-56.png

Share this comment


Link to comment
Share on other sites

Hi! Happy to see things are going as well as they are out there on the bleeding edge! Obviously this is outside of our officially supported setups so we can't promise anything but I'm happy to help you debug!

With the first log I see (after a cascade of intel GMA mappings, presumably one per texture?) the following crash:

Spoiler


Native stacktrace:

    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/OxygenNotIncluded_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so(+0xd8194) [0x7f67112d8194]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/OxygenNotIncluded_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so(+0x5bf37) [0x7f671125bf37]
    /usr/lib/x86_64-linux-gnu/libc.so.6(+0x3f0c0) [0x7f671ba3f0c0]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so(+0x27772) [0x7f671e2c5772]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so(+0x19dd5) [0x7f671e2b7dd5]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so(+0x23994) [0x7f671e2c1994]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so(+0x24152) [0x7f671e2c2152]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so(+0x25a6b) [0x7f671e2c3a6b]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so(glXSwapBuffers+0x55) [0x7f671e2b4115]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/UnityPlayer.so(+0x1854ede) [0x7f671d654ede]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/UnityPlayer.so(+0xaf2522) [0x7f671c8f2522]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/UnityPlayer.so(+0xafe329) [0x7f671c8fe329]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/UnityPlayer.so(+0x163465e) [0x7f671d43465e]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/UnityPlayer.so(+0x16353af) [0x7f671d4353af]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/UnityPlayer.so(+0x162b665) [0x7f671d42b665]
    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/UnityPlayer.so(+0xf0e2ba) [0x7f671cd0e2ba]
    /usr/lib/x86_64-linux-gnu/libc.so.6(+0x8f1da) [0x7f671ba8f1da]
    /usr/lib/x86_64-linux-gnu/libc.so.6(clone+0x44) [0x7f671bb17f44]

Debug info from gdb:

mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb

That looks like it's not in ONI itself but rather in either steam or unity, probably not a lot we can do there except advise you to install gdb so you can get symbols.

 

The second one has something impersonating Klei's servers

Spoiler

KleiMetrics: RemoteCertificateNameMismatch, RemoteCertificateChainErrors

[Version]
  V3

[Subject]
  CN=self-signedKey, O=Sagemcom Ca, C=FR

[Issuer]
  CN=self-signedKey, O=Sagemcom Ca, C=FR

[Serial Number]
  System.Byte[]

[Not Before]
  10/14/2011 08:32:29

[Not After]
  09/20/2111 07:32:29

[Thumbprint]
  87336FCC8F622E66C33E9655FECEE195D5427C24
[Signature Algorithm]
  sha256RSA(1.2.840.113549.1.1.11)

[Public Key]
  Algorithm: RSA
  Length: 1024
  Key Blob: 30 81 89 02 81 81 00 d6 6b a0 26 c8 10 26 4e 93 62 6a fa e8 25 95 24 2a 9f fd e6 b2 e8 7e 18 af 83 29 b8 d8 2f 21 a9 9e 0f 7f 5a 30 43 72 a5 0f a7 58 56 f6 cc 81 37 2a 32 fc b2 27 65 50 49 01 17 b1 29 74 e0 c4 a2 7e a1 8d 12 c1 fd 39 25 9d 78 61 01 ca 25 a8 5d 0d 77 d3 85 43 bc 66 b6 fd d0 0b 00 f1 88 f1 4b 1a 70 ed 3c 95 51 18 ed 77 e3 00 9a 90 0e 1b ea 00 92 69 db 7a f8 13 c5 e7 cb 0d 61 9e 7b 94 8f 02 03 01 00 01
  Parameters: 05 00

[22:44:09.135] [19] [WARNING] 18:44:09 KleiMetrics: Exception getting Request Stream:Error: TrustFailure (A call to SSPI failed, see inner exception.)

but that's not a fatal error, it'll just stop you talking to our servers for analytics and skins and such. The crash looks to be the same one again.

Feel free to share more info once you get it and I'll see if anything jumps out at me. Best of luck!

  • Like 3

Share this comment


Link to comment
Share on other sites

On 6/26/2023 at 6:13 PM, nome said:

Hi! Happy to see things are going as well as they are out there on the bleeding edge! Obviously this is outside of our officially supported setups so we can't promise anything but I'm happy to help you debug!

With the first log I see (after a cascade of intel GMA mappings, presumably one per texture?) the following crash:

  Hide contents


Native stacktrace:

    /home/gpeterso/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/OxygenNotIncluded/OxygenNotIncluded_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so(+0xd8194) [0x7f67112d8194]
  ...

mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb

That looks like it's not in ONI itself but rather in either steam or unity, probably not a lot we can do there except advise you to install gdb so you can get symbols.

Thank you for taking the time to look into this, especially when my setup is so strange.  I'm betting Flatpak is the way of the future, but then, most people with a weird setup have an equally unusual motivation.

Seeing "MonoBleedingEdge" in the stack trace reminds me that the error I Googled earlier led me to a discussion of how someone was packaging an app (Steam?) in Flatpak.  Something in the standard Mono release branch wasn't playing nicely, so they had switched to packaging the bleeding-edge branch which fixed their problem.  Maybe the bleeding-edge branch has a bug that's causing my crashes?

Do you know if a native Steam/Linux install requires MonoBleedingEdge?  If not, then this is probably a growing pain of Mono in Flatpak or the choices the Steam Flatpak package maintainers have made.  I guess I could do a native install to find out.

Maybe it will get better if I just wait.  If not, having a suspicion may give me an idea of what to try next.  Thanks again!

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