Heh thats why I say it will never be fixed.
Really Ryan, I've located the thread that stalls the server in such occassions long ago. This is not the main thread and not the timer thread, this is one of the packet handling threads. The thread that stalls everything does some omnious processing inside Server.Network.NetState.OnSend - how can this be the custom script? I cant even look what exactly it does and never quits doing, because there is no source code for this method. And this because this is part of the core.
Also I removed all custom scripts besides absolutely elementary ones (that just tweak some constants as gain speed and such). But as I said, I am not a stranger to debugging (to put it mildly), and if this was the ordinary custom script bug, I'd caught it long ago.
Also about memory. It uses only 400-450 Mb, we have 1Gb, this is
not the "no memory condition", even for .NET. Maybe adding more memory can postpone this bug, but I hope that source of it can be eliminated in first place.