After reviewing my 'fix', actually what was happening is that it was making the application crash, which is why the application memory was not increasing...
Anyhow I think there should be only 1 instance of NonLeakySubcomponent in memory at any time, irregardless of whether the GC would collect it or not. I'll keep on looking into it. -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Memory-leak-caused-by-addChild-tp51677p51729.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
