I've experienced this issue and determined the cause.
It is a rather intricate problem with how we are handling object creation (and deletion/cleanup) in JS, and thus will take some time to fix. For now, just try not to 'wipe an excessive amount (I find with a full world one wipe nearly doubles the amount of RAM usage UOX3 has, and the second wipe generally crashes).
As giwo writes in this thread, there are currently some issues with the JS engine which cause this crash.
As a workaround, use 'AREACOMMAND WIPE instead of 'WIPE, since it uses a different way of iterating through the items, and shouldn't crash the server (at least, it hasn't for me).
Ideally the JS engine shouldn't crash at all, so I am still hoping there is some way to catch it before it crashes alltogether.... however, having said that, yes, normal usage of 'wipe should work fine now.
Running a program like UOX3 on a machine with low-memory is asking for it.
However, as I noted, I would like to find a way to check for enough free memory before allocating new JS Objects... sadly I have not yet found a way...
giwo wrote:Running a program like UOX3 on a machine with low-memory is asking for it.
My server machine has 512MB RAM and just for testing I multiplied the item spawns by 10 (simulating users that collect as much items as possible) and memory usage easly went way over 512MB when doing 'cleanup. Most affordable consumer server you can rent here have around 512MB RAM.