Hi Alex, Clint, I've finally reproduced the behaviour that you mention, only that I've had to set the timer to 10 seconds. In that situation, forcing a garbage collection from profiler frees some instances, so the number of total instances is lower than Cumulative instances, without changing the code. So you're right, instances get eventually freed by GC. (However using smaller timer intervals still show me an equal number of cumulative instances and instances and memory increasing indefinitely, even forcing a garbage collection.)
However it still worries me the apparent behaviour of this simple application. It would be better to actually remove the object reference that is causing the instance to stay in memory so it is effectively removed. I guess it is not immediately removed because there's a circular reference, which makes the GC to not remove it quickly. With my 'fix' I'm removing the circular reference, hence Flash Profiler reports only 1 instance of NonLeakySubcomponent ever and memory stays constant, otherwise objects accumulate in memory until GC eventually collects them. Regards! -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Memory-leak-caused-by-addChild-tp51677p51728.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
