Need some more Anti Crash ideas (Not asking for ANY code or any RP Mods) - Developers

I run a sandbox build server and maintain my own admin toolbox kinda thing. It houses any improvements to the game I care to write. Recently, the servers been extremely unreliable (I personally blame PointShop. It always seems to bring stability down.) with nothing suspicious in the console. What I am asking is, appart from physics related things, what else can cause instability? Iv already got anti spam, spaz prevention, cant spawn things on top of eachother done and now im looking to write some more prevention stuff. Idea Bin ======= Anti Spam X Anti Spaz X Anti Spawn stuff on top of eachother X Anti Prop push X Anti Unfreeze All (RR Prevention, Make spherical crashes server if you RR) X Server Information (Shows me the function count, LUA ram etc) X Anything else you can think of, please let me know. I personally feel alot of Server owners are getting scared off from sandbox as its so much easier to make a (insert color here):RP server which is a hell of alot more reliable and quicker to setup.

Remove the wooden bench, enforce a prop limit suitable for your server max players, disallow wire processors, remove ropes, get admins to clear client side rag dolls/decals often. You could also try profiling hooks and see if any are really laggy.

Why remove the bench? Stacker spam? Cant really enforce a prop limit, thats one major reason people build here Why remove processors? Guessing there really badly optimised. Remove ropes? as in the clientside drawing? Profiling is something I am very interested in looking into. How do you do it? is it part of the Debug library?

-Crap

-Snip

Again, lack of sleep has given me the effects. Sorry man, was reading some other topic then I went back to the facepunch after 2 hours and posted it in a wrong place. I'll go get some sleep.

Oh, sorry. I kinda went off the rails a little too, I thought you were genuinly saying this didn't belong here. NP Man, go get some sleep!

Pointshop = Server Instability? Might pointshop be the reason why srcds.exe crashes with "Not Responding" every now and then?

Dont quote me on that, but from my experience it does seem to be.

[QUOTE=monkstick;41758188]Dont quote me on that, but from my experience it does seem to be.[/QUOTE] Is it "Not Responding" crash or Crazy Physics/Engine crash? Also, did removing pointshop fix it? I will also test it on my server for temporarily removing the addon for a week.

Neither. I dont get a tool used, prop spawned, crazy physics, nothing. It just stops responding. ANYWAY, back on topic please.

Anyways, I just woke up. You should add a security againist props that get out of the map because they are the main reason for server crashes.

[QUOTE=monkstick;41758935]Neither. I dont get a tool used, prop spawned, crazy physics, nothing. It just stops responding. ANYWAY, back on topic please.[/QUOTE] When a program is 'not responding', it is usually caused by an infinite loop. It's possible to write Lua code that runs in an infinite loop and subverts Garry's checking mechanism (unintentionally too!). If the loop is happening in Lua code, you could use my [url=http://facepunch.com/showthread.php?t=1005357]debugger[/url] to break execution while it's not responding, and see if it lands you inside a Lua function. If nothing happens, then the loop is happening in C++ code somewhere, and you should consider using [url=http://technet.microsoft.com/en-us/sysinternals/bb896653]Process Explorer[/url] to forcefully generate a minidump and send that dump to Garry.

[QUOTE=Jcw87;41769420]When a program is 'not responding', it is usually caused by an infinite loop. It's possible to write Lua code that runs in an infinite loop and subverts Garry's checking mechanism (unintentionally too!). If the loop is happening in Lua code, you could use my [url=http://facepunch.com/showthread.php?t=1005357]debugger[/url] to break execution while it's not responding, and see if it lands you inside a Lua function. If nothing happens, then the loop is happening in C++ code somewhere, and you should consider using [url=http://technet.microsoft.com/en-us/sysinternals/bb896653]Process Explorer[/url] to forcefully generate a minidump and send that dump to Garry.[/QUOTE] To my knowledge my code is clean, but I shall keep your debugger ready just in case. Thanks a lot! OT: One thing that really worked for me is no colliding ragdolls.