Server Crashing After Several Hours, Runtime Error

[Wicked]

My dedicated server keeps crashing after being hosted for several hours(3-4 usually) with 20+ players in it constantly with no errors in the Blockland console. The error window that pops up is a Runtime Error, with no error code number. The used physical memory in the Task Manager and Resource Monitor Windows never gets close to filling up, but the commit charge does, and it seems to crash when the commit charge memory fills up to 100%. After monitoring the commit memory, it goes up and down but it seems to slowly build up the longer the server is running as more people join and do things in the server. What exactly causes the commit charge to keep increasing when the used physical memory stays quite constant, based on the number of players in the server etc?

[Ad Bot]

[Compy]

memory leaks maybe? are you deleting every object that you create (via torquescript) after you're done using them? ie. sometimes scripters will create ScriptObjects and never delete them, and they build up over time. slowly but surely.

[Wicked]

memory leaks maybe? are you deleting every object that you create (via torquescript) after you're done using them? ie. sometimes scripters will create ScriptObjects and never delete them, and they build up over time. slowly but surely.

I guess it's possible, I'll need to look into it. Out of curiosity, how would that effect only the commit memory and not used physical memory?

[Compy]

the commit limit isnt even related to free memory. you can read all about it here:

http://superuser.com/questions/482678/commit-charge-is-100-full-but-physical-memory-is-just-60-when-using-no-page-fi

if you want to you can increase your page file size a couple GB and your server will last a while longer but the death is still inevitable.

[Goth77]

Windows 7/8 manages the page file pretty efficiently. I would recommend setting your page file in virtual memory to system managed size if it isn't already.

Try to cut back on the processes you have running in the background when your dedicated server is running.