IVM heap usage & game objects
-
What i am observing is an increased general cost for all my functions when the heap is "flatlining". Calling my own gc functions had no effect, same as calling the offical gc(). Only a code upload resets the heap for me.
-
Could that be some gc death loop?
Where it tries to remove garbage that somehow links to it self until it decides to give up and wait for the next tick?
-
That brings me to an idea,
try to build up artificial garbage over some ticks and then delete it.
It would be interesting to see if that has any effect.