Exiting game crashes to desktop (linux)

HI,

I can confirm.I am hit by this very bug too.

Can also confirm, Linux Mint here.

Same here,

Old game crashed on exit after update to A21 and my mini bike disappeared. Running on Arch Linux. So wiped the data as instructed and started new map. All vanilla no mods installed. And same crash on exit.

Here is link to:
output_log_client__2023-11-29__21-35-57.txt: https://pastebin.com/YXQs6gbe
map_info.xml: https://pastebin.com/xT67i3vD

Same crash constantly happens here.

 

Game Version: A21.2 (b30)

Arch Linux

OpenGL renderer string: AMD Radeon RX 580 Series (polaris10, LLVM 16.0.6, DRM 3.54, 6.6.3-zen1-1-zen)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.2.1-arch1.2
OpenGL core profile shading language version string: 4.60

 

here's gdb backtrace

 

Thread 134 "DymeshThread1" received signal SIG37, Real-time event 37.
[Switching to Thread 0x7ffc587fa6c0 (LWP 346036)]
0x00007ffff5aa74ae in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7ffc587f96e8, op=137, expected=0, futex_word=0x7fff5e1b6f10) at futex-internal.c:57
57          return INTERNAL_SYSCALL_CANCEL (futex_time64, futex_word, op, expected,
(gdb) 
(gdb) 
(gdb) 
(gdb) bt
#0  0x00007ffff5aa74ae in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7ffc587f96e8, op=137, expected=0, futex_word=0x7fff5e1b6f10) at futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7fff5e1b6f10, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7ffc587f96e8, private=private@entry=0, cancel=cancel@entry=true)
    at futex-internal.c:87
#2  0x00007ffff5aa752f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7fff5e1b6f10, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7ffc587f96e8, private=private@entry=0)
    at futex-internal.c:139
#3  0x00007ffff5aaa055 in __pthread_cond_wait_common (abstime=0x7ffc587f96e8, clockid=1, mutex=0x7fff5e1b6ec0, cond=0x7fff5e1b6ee8) at pthread_cond_wait.c:503
#4  ___pthread_cond_timedwait64 (cond=0x7fff5e1b6ee8, mutex=0x7fff5e1b6ec0, abstime=0x7ffc587f96e8) at pthread_cond_wait.c:643
#5  0x00007fff5de4e887 in ?? () from /home/max/fast/SteamLibrary/steamapps/common/7 Days To Die/7DaysToDie_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#6  0x00007fff5de57a96 in ?? () from /home/max/fast/SteamLibrary/steamapps/common/7 Days To Die/7DaysToDie_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#7  0x00007fff5ddfe12e in ?? () from /home/max/fast/SteamLibrary/steamapps/common/7 Days To Die/7DaysToDie_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#8  0x00007fff5ddae735 in ?? () from /home/max/fast/SteamLibrary/steamapps/common/7 Days To Die/7DaysToDie_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#9  0x00000000406054c6 in ?? ()
#10 0x00007ffc33ffa3c0 in ?? ()
#11 0x00007ffd4fd6dd80 in ?? ()
#12 0x00007ffd4fd6dd80 in ?? ()
#13 0x00007ffd4fd6dd80 in ?? ()
#14 0x0000000000000064 in ?? ()
#15 0x00007ffc24001f50 in ?? ()
#16 0x00007ffc587f9950 in ?? ()
#17 0x00007ffc587f9860 in ?? ()
#18 0x00007ffd4fd6dd01 in ?? ()
#19 0x000000004060540c in ?? ()
#20 0x00007ffc29ced0f0 in ?? ()
#21 0x0000000000000000 in ?? ()

 

Have found a workaround that was inspired by running it through gdb.

 

When exiting the game mono sends various signals, so in gdb those must be ignored by:

`handle SIGXCPU SIG33 SIG35 SIG36 SIG37 SIGPWR nostop noprint`

 

Seems that steams launches game through steam-launch-wrapper which intercepts crashes and in this case "signal SIG37, Real-time event 37" which is signaled during exit to main menu and causes the process to crash.

 

I solved it here by launching game manually using 7DaysToDie.x86_64 instead of using steam.

Direct launching the game worked only one time. Second launch simply did not start the gameprogram.

 

I just discovered that when the gameprogram is offline (steam has no internet connection during reboot of the router) that exiting a game did not crash the gameprogram.

 

So maybe some telemetry code causing the crash?

 

51 minutes ago, KoolaLobita said:

Direct launching the game worked only one time. Second launch simply did not start the gameprogram.

 

I just discovered that when the gameprogram is offline (steam has no internet connection during reboot of the router) that exiting a game did not crash the gameprogram.

 

So maybe some telemetry code causing the crash?

 

 

The game won't start if steam is not running in the background.

So make sure steam is running in the background and then launch manually

After a Steam update the program doesn't crash to the desktop anymore.

This should have been resolved with Steam updates, from light research. If it's still doing this, please report the crash/Distro you're using here though, with a mention to me