TF2 server crashing with glibc error

[kilorat]

OS: Centos linux 5.7 64-bit
CPU: E5530 xeon

Since the big TF2 update, the server can't go 3 maps without crashing, it just happens at random times, I don't know the trigger for the crashing yet.

I disabled all mods (no .vdf files in plugins/ at all), and it still crashes.

It shows this on the console

Code:

*** glibc detected *** ./srcds_linux: double free or corruption (!prev): 0x0a106ed8 ***
======= Backtrace: =========
/lib/libc.so.6[0x9ed6c5]
/lib/libc.so.6[0x9ef8dc]
/lib/libc.so.6(realloc+0xe6)[0x9f04a6]
bin/libtier0.so[0xf7f5fa34]
/data/home/nom/steam/orangebox/bin/engine.so[0xf75fae0d]
/data/home/nom/steam/orangebox/bin/engine.so[0xf75f5b17]
/data/home/nom/steam/orangebox/bin/engine.so[0xf75f5848]
/data/home/nom/steam/orangebox/bin/engine.so[0xf75f638c]
/data/home/nom/steam/orangebox/bin/engine.so[0xf764c01c]
/data/home/nom/steam/orangebox/bin/engine.so[0xf765f45a]
/data/home/nom/steam/orangebox/bin/engine.so[0xf766424a]
/data/home/nom/steam/orangebox/bin/engine.so[0xf76640ec]
bin/libvstdlib.so[0xf7ea82b4]
bin/libvstdlib.so[0xf7ea9fef]
bin/libvstdlib.so[0xf7eaa36e]
bin/libtier0.so(_ZN7CThread10ThreadProcEPv+0x97)[0xf7f62817]
/lib/libpthread.so.0[0xaeb832]
/lib/libc.so.6(clone+0x5e)[0xa5645e]
======= Memory map: ========
00965000-00980000 r-xp 00000000 08:03 17727505 /lib/ld-2.5.so
00980000-00981000 r--p 0001a000 08:03 17727505 /lib/ld-2.5.so
00981000-00982000 rw-p 0001b000 08:03 17727505 /lib/ld-2.5.so
00984000-00ad7000 r-xp 00000000 08:03 17727489 /lib/libc-2.5.so
00ad7000-00ad9000 r--p 00153000 08:03 17727489 /lib/libc-2.5.so
00ad9000-00ada000 rw-p 00155000 08:03 17727489 /lib/libc-2.5.so
00ada000-00add000 rw-p 00ada000 00:00 0
00adf000-00ae2000 r-xp 00000000 08:03 51707937 /lib/libdl-2.5.so
00ae2000-00ae3000 r--p 00002000 08:03 51707937 /lib/libdl-2.5.so
00ae3000-00ae4000 rw-p 00003000 08:03 51707937 /lib/libdl-2.5.so
00ae6000-00afb000 r-xp 00000000 08:03 17727507 /lib/libpthread-2.5.so
00afb000-00afc000 r--p 00015000 08:03 17727507 /lib/libpthread-2.5.so
00afc000-00afd000 rw-p 00016000 08:03 17727507 /lib/libpthread-2.5.so
00afd000-00aff000 rw-p 00afd000 00:00 0
00b01000-00b28000 r-xp 00000000 08:03 51707947 /lib/libm-2.5.so
00b28000-00b29000 r--p 00026000 08:03 51707947 /lib/libm-2.5.so
00b29000-00b2a000 rw-p 00027000 08:03 51707947 /lib/libm-2.5.so
00bcc000-00bd3000 r-xp 00000000 08:03 17727509 /lib/librt-2.5.so
00bd3000-00bd4000 r--p 00007000 08:03 17727509 /lib/librt-2.5.so
00bd4000-00bd5000 rw-p 00008000 08:03 17727509 /lib/librt-2.5.so
08048000-08049000 r-xp 00000000 08:03 36307178 /data/home/nom/steam/orangebox/srcds_linux
08049000-0804a000 rw-p 00000000 08:03 36307178 /data/home/nom/steam/orangebox/srcds_linux
085fc000-0fde2000 rw-p 085fc000 00:00 0 [heap]
e04fe000-e24ff000 rw-p e04fe000 00:00 0
e24ff000-e2500000 ---p e24ff000 00:00 0
e2500000-e2f00000 rwxp e2500000 00:00 0
e2f00000-e2fa5000 rw-p e2f00000 00:00 0
e2fa5000-e3000000 ---p e2fa5000 00:00 0
e3100000-e32fe000 rw-p e3100000 00:00 0
e32fe000-e3300000 ---p e32fe000 00:00 0
e3300000-e3500000 rw-p e3300000 00:00 0
e3500000-e3700000 rw-p e3500000 00:00 0
e3700000-e3800000 rw-p e3700000 00:00 0
e3900000-e3b00000 rw-p e3900000 00:00 0
e3b00000-e3bfe000 rw-p e3b00000 00:00 0
e3bfe000-e3c00000 ---p e3bfe000 00:00 0
e3c00000-e3d00000 rw-p e3c00000 00:00 0
e3d00000-e3f00000 rw-p e3d00000 00:00 0
e3f00000-e40ff000 rw-p e3f00000 00:00 0
e40ff000-e4100000 ---p e40ff000 00:00 0
e4100000-e4300000 rw-p e4100000 00:00 0
e4300000-e4500000 rw-p e4300000 00:00 0
e4500000-e45fe000 rw-p e4500000 00:00 0
e45fe000-e4600000 ---p e45fe000 00:00 0
e4600000-e4700000 rw-p e4600000 00:00 0
e4700000-e4900000 rw-p e4700000 00:00 0
e4900000-e49fe000 rw-p e4900000 00:00 0
e49fe000-e4a00000 ---p e49fe000 00:00 0
e4a00000-e4b00000 rw-p e4a00000PreMinidumpCallback: updating dump comment
Fri Oct 14 21:54:13 PDT 2011: Server Quit

I thought by now every forum would be filled with this, but I'm not finding anyone else with this problem, so now I'm wondering, what quirky thing about my setup could even do this?
I'll continue troubleshooting, and I can figure this out, but at this point I'm just trying to feel out if anyone else ran into this, or if there's an area I should be looking at first.

[linda68]

The error message suggests that the server is crashing due Snow Rider 3D to a memory-related issue, specifically a double free or corruption error. This error can occur when the program attempts to free memory that has already been freed or when memory corruption has occurred.