Page MenuHomeFeedback Tracker

Linux DayZ Server Experimental 1.14.154166 - Crash when Ctrl+C is pressed to stop server
Assigned, NormalPublic

Description

I've been giving the new Linux experimental server a try but I've noticed that when I press Ctrl+C to stop the server, it crashes with a segmentation fault:

15:27:52   Primary Spawner: "Vehicle", active: yes, repeat: 1
15:27:52 [42] VehicleTruck01
15:27:52   Primary Spawner: "Vehicle", active: yes, repeat: 1
15:27:52 [CE][Hive] :: Initializing of spawners done.
15:27:52 [CE][Hive] :: Init sequence finished.
15:27:52 Player connect enabled
15:27:52 Mission read.
15:27:52 Connected to Steam
15:27:52 Steam policy response
15:27:52 [IdleMode] Entering IN - save processed
^C15:28:24 
Unreachable
Received fatal signal: SIGSEGV(11)	PID: 8651
***** SIGNAL SIGSEGV (11)
exitWithDefaultSignalHandler:156. Exiting due to signal, 11
Segmentation fault (core dumped)

Here is a backtrace of the crash, generated using gdb:

Reading symbols from ./DayZServer...
(No debugging symbols found in ./DayZServer)
[New LWP 7600]
[New LWP 7593]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./DayZServer -config serverDZ.cfg -profiles=profile'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007ffe45d18801 in gettimeofday ()
[Current thread is 1 (Thread 0x7f103320d700 (LWP 7600))]
(gdb) thread apply all bt

Thread 2 (Thread 0x7f1031bb0ac0 (LWP 7593)):
#0  0x00007f1032c8e33d in musable (mem=0x307adb10) at malloc.c:4843
#1  __malloc_usable_size (m=0x307adb10) at malloc.c:4867
#2  0x00000000009481be in ?? ()
#3  0x000000000094952e in ?? ()
#4  0x00000000009734bc in ?? ()
#5  0x0000000000973373 in ?? ()
#6  0x0000000000972e89 in ?? ()
#7  0x00000000009723c8 in ?? ()
#8  0x00007f1032c38a27 in __run_exit_handlers (status=11, listp=0x7f1032dda718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108
#9  0x00007f1032c38be0 in __GI_exit (status=<optimized out>) at exit.c:139
#10 0x0000000000d157ef in ?? ()
#11 0x0000000000d164d6 in ?? ()
#12 <signal handler called>
#13 0x0000000000a8ffa7 in ?? ()
#14 0x00000000005e220f in ?? ()
#15 0x00000000009f4e71 in ?? ()
#16 0x00000000005e2541 in ?? ()
#17 0x000000000055ed25 in ?? ()
#18 0x00007f1032c160b3 in __libc_start_main (main=0x55ecc0, argc=4, argv=0x7ffe45c56618, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe45c56608) at ../csu/libc-start.c:308
#19 0x00000000005d3eda in ?? ()

Thread 1 (Thread 0x7f103320d700 (LWP 7600)):
#0  0x00007ffe45d18801 in gettimeofday ()
#1  0x0000000000865eae in ?? ()
#2  0x0000000000f7c8d5 in ?? ()
#3  0x0000000000865012 in ?? ()
#4  0x00000000008650b9 in ?? ()
#5  0x00007f1033136609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f1032d11293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Linux x64
Operating System Version
Ubuntu 20.04
Category
Game Crash
Steps To Reproduce
  1. Start Linux experimental server
  2. Wait for server to finish initializing
  3. Press Ctrl+C to stop the server
  4. Observe crash

Event Timeline

tjensen created this task.Sep 8 2021, 10:29 PM
tjensen renamed this task from Linux DayZ Server Experimental 1.14 - Crash when Ctrl+C is pressed to stop server to Linux DayZ Server Experimental 1.14.154166 - Crash when Ctrl+C is pressed to stop server.
tjensen changed Reproducibility from N/A to Always.Sep 8 2021, 10:32 PM
gOOvER added a subscriber: gOOvER.Sep 9 2021, 11:38 AM
Geez changed the task status from New to Assigned.Sep 9 2021, 3:39 PM
Robalo added a subscriber: Robalo.EditedSep 9 2021, 6:36 PM

Similar crash here, except it happened for no apparent reason after about 1h runtime:

19:19:43 [CE][VehicleRespawner] (PRIContaminatedArea) :: Initial random enabled for "StaticContaminatedArea" - Chosen nomin
al: 0
19:19:43 [CE][VehicleRespawner] (PRIContaminatedArea) :: Initial random enabled for "StaticContaminatedArea" - Chosen nomin
al: 0
19:20:09 Warning Message: No entry 'bin\config.bin/CfgVehicles/ZmbM_Jacket_blue.P3DAttachments'.
19:20:09 Warning Message: No entry '.P3DProxies'.
19:20:09 Warning Message: No entry '.BoneNames'.
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: No entry 'bin\config.bin/CfgVehicles/ZmbF_JoggerSkinny_Blue.P3DAttachments'.
19:20:09 Warning Message: No entry '.P3DProxies'.
19:20:09 Warning Message: No entry '.BoneNames'.
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: No entry 'bin\config.bin/CfgVehicles/ZmbM_VillagerOld_Blue.P3DAttachments'.
19:20:09 Warning Message: No entry '.P3DProxies'.
19:20:09 Warning Message: No entry '.BoneNames'.
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: Size: '/' not an array
19:20:09 Warning Message: Size: '/' not an array
Received fatal signal: SIGSEGV(11)      PID: 20139
***** SIGNAL SIGSEGV (11)
exitWithDefaultSignalHandler:156. Exiting due to signal, 11

more info from coredump: https://pastebin.com/ukSH6cas

I reproduce the crash on CTRL+C as well.

This has always happened on Arma servers in the past. Probably not a big deal if you are taking the server down anyway - so long as the persistence files aren't corrupted.

raxto added a subscriber: raxto.Sep 13 2021, 10:26 PM