3 Replies Latest reply on Jun 7, 2011 7:30 AM by tyuiop86





      My problem is my Flex app would eats up memory over long period of browsing different states/screens because they never get destroyed. I am thinking about setting all my 'screen components' itemDestructionPolicy to auto.


      Can anyone give me some tips/guidance if this is a good idea ? Some people are saying that it is better to never destroy components, because it takes longer time to rebuild a screen, but how would I solve this memory problem  ?