Well, i managed to stabilize the childconstraintinfo
but the cumulative memory and the cumulative instances of it still increases. So my problem remains
although the childconstraintinfo instances do not increase anymore. Any ideas?
Memory leaks are usually not related to cumulative instances, just current
May I ask how you got the ChildConstraintInfo instances to stabilize?
I am having a very similar problem in what sounds like a very similar project. I'm building a lot of "slides" which are dynamically generated and destroyed, and loop over and over. I am having a problem with continuously expanding ChildContstratinInfo instances (current instances, not just cumulative). The expanding instances eventually take up all the available memory. From what I can glean from the profiler, it seems to be related to the Image component, but I have not been able to figure out beyond that.
Thanks god, I did managed to solve my problem! The whole concept is to make all the variable that you use null when you do not need them anymore! For example
I had a cnavas with four children (eg images). After an interval i want to reuse the canvas and load 4 other images. the correct way to do this is:
image2 = null;
image4 = null;
parentCanvas = null;
parentCanvas = new Canvas()
imageX = new Image() X=1,2,3,4
Also mind to remove all the listeners of an object before you make you object null.
The whole concept is : At the end of every function make all the variables that you use NULL and remove all the children and the listeners!
Doing this the garbage collector will do miracles!
And also if you use the settimeout try not to use parameters. for example do not use
timeout = setTimeout(delaytime, timerFunction, param1, param2, paramN)
but try to use just
timeout = setTimeout(delaytime, timerFunction)