Skip to content

DestroyArea leaving behind some bad juju

It seems 'something' is being left behind after calling Destroy area. The area deletes just fine, I've done several tests showing that (show area count / output string on successful delete), but processing load will continue to increase for each area added/deleted.

You can simply make an area, fill it with 20 placeables, and create a trigger to clone the area and another trigger to delete the clone. Keep making clones and delete them, and you'll find your server CPU usage goes up after every deletion until you eventually max out.

Within ~50 uses of areaCreate/areaDelete I can take a server running at 1.7% to 100%.

Comments

Sign In or Register to comment.