SegFault when playing L4D2

[halfbit]

Hi!

I have this extremely annoying error that prevents me from playing any L4D2 round with friends on my server because it crashes on every single map after some time.

It usually starts about 5 minutes into a map by giving that error first:

Code:

threadtools.cpp (2683) : Assertion Failed: Failed to create thread (error 0xb)
Assert( Assertion Failed: Failed to create thread (error 0xb) ):/home/buildbot/buildslave_steam/steam_rel_client_linux/build/src/tier0/threadtools.cpp:2683

and then by spamming this over and over again:

Code:

...
threadtools.cpp (2683) : Assertion Failed: Failed to create thread (error 0xb)
threadtools.cpp (2683) : Assertion Failed: Failed to create thread (error 0xb)
threadtools.cpp (2683) : Assertion Failed: Failed to create thread (error 0xb)
...

Then, after 10-30 minutes of it spamming that (usually at the end of the map), it crashes with this error:

Code:

...
threadtools.cpp (2683) : Assertion Failed: Failed to create thread (error 0xb)
***** OUT OF MEMORY! attempted allocation size: 1048576 ****

CAsyncIOManager: 0 threads terminating.  0 reads, 0 writes, 0 deferrals.
CAsyncIOManager: 0 single object sleeps, 0 multi object sleeps
CAsyncIOManager: 0 single object alertable sleeps, 0 multi object alertable sleeps
configstore.cpp (96) : Assertion Failed: ConfigStore (InstallConfigStore) is dirty, and being destroyed, we're discarding data
framefunction.cpp (120) : Assertion Failed: CFrameFunctionMgr::~CFrameFunctionMgr: non static FrameFunction still registered
Assert( Assertion Failed: CFrameFunctionMgr::~CFrameFunctionMgr: non static FrameFunction still registered ):/home/buildbot/buildslave_steam/steam_rel_client_linux/build/src/common/framefunction.cpp:120

Segmentation fault (core dumped)
BFD: Warning: /opt/hlds/left4dead2/core is truncated: expected core file size >= 4217651200, found: 143650816.
Cannot access memory at address 0xf77ef8f0
Cannot access memory at address 0xffecf19c
/opt/hlds/left4dead2/debug.cmds:4: Error in sourced command file:
Cannot access memory at address 0xf77ef8f0
email debug.log to linux@valvesoftware.com

debug.log:

Code:

----------------------------------------------
CRASH: So 28. Okt 15:39:11 CET 2012
Start Line: ./srcds_linux -autoupdate -debug -port 27015 -game left4dead2 +maxplayers 8 -ip nope.bz +map c1m1_hotel
[New Thread 8250]
[New Thread 8272]
#0  0xed723f22 in ?? ()
No symbol table info available.
eax            0xb      11
ecx            0x96fd1ec        158323180
edx            0x96fd16c        158323052
ebx            0xf6ed517c       -152219268
esp            0x96fd15c        0x96fd15c
ebp            0xffecf198       0xffecf198
esi            0x1314c  78156
edi            0x5df    1503
eip            0xed723f22       0xed723f22
eflags         0x10202  [ IF RF ]
cs             0x23     35
ss             0x2b     43
ds             0x2b     43
es             0x2b     43
fs             0x0      0
gs             0x63     99
End of Source crash report
----------------------------------------------

gdb backtrace:

Code:

Reading symbols from /opt/hlds/left4dead2/srcds_linux...(no debugging symbols found)...done.
BFD: Warning: /opt/hlds/left4dead2/core is truncated: expected core file size >= 4216946688, found: 142606336.
[New Thread 28239]
[New Thread 28261]
Cannot access memory at address 0xf773b8f0
(gdb) bt
#0  0xed66ff22 in ?? ()
Cannot access memory at address 0xffada48c

server.cfg

Server OS: Debian Squeeze, kernel 2.6.32-5-amd64, x86_64
Processor: Intel Core i7-2600
Ram: 32GB
Game: Left 4 Dead 2
Start Up Command: (RDTSC_FREQUENCY is set to '3411.000000') ./srcds_run -autoupdate -debug -port 27015 -game left4dead2 +maxplayers 8 +map c2m1_highway -ip 5.9.22.239


I have no idea what to do and this is getting seriously frustrating as I also can't find anything useful by googling etc.

If anyone has any tips or help, thanks a lot!

[koz]

When was the last time you updated your server? If you haven't updated it in a while, then I advise updating then running your server again.

The whole "threadtools.cpp (2683)" was a problem that happened a while ago with the steam libraries.

[halfbit]

(10-29-2012, 10:25 PM)koz Wrote:  When was the last time you updated your server?

It auto updates every time it gets started and I just "forcibly" updated it (`./steam -command update`) yesterday, so everything is up to date.