This content has been marked as final. Show 2 replies
One thing about Flash Player 9 that is important to know is that
internally, it uses garbage collection to keep track of when certain
objects need to be freed. This means that tracking leaks is not as
simple as running Windows Task Manager and watching the Mem Usage
column, or something like that -- it is much more subtle than that.
Garbage collection is a great thing in general, but it does
unfortunately mean that you can't just tell "at a glance" if an
application is leaking memory. There really isn't a quick and easy way
to spot a memory leak, because the exact heuristics can be very subtle.
In the case you describe, I wouldn't worry about it. But if you see a
steady and significant increase in memory over a long period of time,
then that could indicate a real problem.
- Mike Morearty
Flex Builder team
> is anyone else having memory leak issues w/ the 3rd beta? i've taken basically
> everything out of my app and just have a tab navigator and i'm still leaking
> memory after each click... and the event listener isn't even doing anything
> when it receives the event! so i'm curious if i should be worried about this &
> other stuff or if i should not bother until the final product....
ahhh.... though when i bring my whole app on (instead of the small portion of it), the memory does significantly increase (watching the task manager). but i suppose since i've not received a memory error just yet, i'll wait. i am careful to remove event listeners & children's children, etc....