Memory climbs rapidly during CSG updates in example

[gkjohnson]

Possible sources:

• *debugger info (should possibly allow for disabling this in the demo?)
• raycast hit object creation (could be fixed by #3)
• list of intersection ids

[gkjohnson]

With debug info disabled the memory increases much less drastically but still enough to do something about it. Raycast results and triangle index storage likely account for most of the memory allocated.

[gkjohnson]

Now it seems like there's a memory leak somewhere:

up to ~950mb

[gkjohnson]

Memory is now under control - other memory is heavily related to raycasting memory allocation.