Post here with any issues with the new COD4x server 74.91.119.86:28960 >XI< MW2 Freezetag c4x

[iboomboom]

It's patched... 

[iboomboom]

I used bots to cover the scenarios that could potentially create the leaks. It withstood the beating for 1 hour then we had people play for 3 hours. It crashed once early morning when people started joining in then quickly self recovered. I was able to use that to patch the new leak source. 
Synthetic testing can only do so much, real life in-game interactions brings out previously undiscovered behaviors. 

[iboomboom]

I have patched over 15 mod files with leaky buckets. I am running a stress test with bots. If you happen to see them, thank them for their untiring service. 

I do need real people to play and try to break it. We are 90% there, I just need some real crazy human gameplay to prove that its all done.

[iboomboom]

When the server hung twice today, I was ready to call it quits with getting this mod to stabilize on CoD4x server. After reviewing the console log from the first hang, I am hopeful this is the final leak in the bucket. I patched two files for the following bugs.

- Slow drip leak due to long per player threads starting at every round switch. The more players on the server and the more rounds they play on a single map the leak becomes bigger. Certain maps can exacerbate this condition. It was originally not discovered because it wasn't the focus. 

- Extra 5th round bug. This happened due to a race condition. Multiple threads were touching the score limit check and on occasion would update the final score even though the score limit was reached. I have added safeguards to prevent this from happening. 

I run a watchdog service that monitors the game server and if it is hung, it will restart the server. I have enhanced this watchdog to perform deep process state captures before restarting. This way even if there is still some gremlin hiding somewhere bringing out its sneaky head, I will have the full trace of where to find it. 

Edited 7 hours ago by iboomboom

[iboomboom]

FYI, this happened this morning. This happened because in that brief moment the server wasn't able to auth a client with Steam's network. I have since disabled steam authorization so we don't run in to these issues for the time being.
 

Going from CS_FREE to CS_CONNECTED for BiggieUK>XI<ADM num 0 from: 82.7.234.148:28960<=>74.91.119.86:28960
This program has crashed with signal: Segmentation fault
The current Gameversion is: CoD4 X - linux-i386-custom type 'e' build 1222 Jun  8 2026
File is cod4x18_dedrun Hash is: b2e575b23763e28cf28878d1fde59a7e0174eaa60c221b041598a41630f38ec4
---------- Backtrace ----------
   20: cod4x18_dedrun(Sys_PrintBacktrace+0x31) [0x566fd32b]
   19: cod4x18_dedrun(Sys_DumpCrash+0x9d) [0x566fd411]
   18: cod4x18_dedrun(Sys_SigHandler+0x24) [0x566fd498]
   17: linux-gate.so.1(__kernel_sigreturn+0) [0xf7240590]
   16: ./steam_api.so(+0x1ff1e) [0xe120df1e]
   15: ./steam_api.so(+0x202b2) [0xe120e2b2]
   14: ./steam_api.so(+0x1ada0) [0xe1208da0]
   13: ./steam_api.so(+0x1b578) [0xe1209578]
   12: cod4x18_dedrun(SV_ConnectSApi+0x29) [0x567501dd]
   11: cod4x18_dedrun(SV_SendClientGameState+0x61) [0x56760226]
   10: cod4x18_dedrun(SV_ExecuteClientMessage+0x142) [0x567623a2]
    9: cod4x18_dedrun(NET_UDPPacketEvent+0x66) [0x56725107]
    8: cod4x18_dedrun(NET_Event+0x8c) [0x567799ec]
    7: cod4x18_dedrun(NET_Sleep+0x1c9) [0x56779c09]
    6: cod4x18_dedrun(SV_Frame+0x2f9) [