Two places to learn about weak refs and memory: http://livedocs.adobe.com/flex/201/html/16_Event_handling_172_6.html, http://livedocs.adobe.com/flex/201/html/performance_118_27.html When I say removing children from the display list I mean that for every addChild call you make, if the component you added is meant to go away forever, make sure to call removeChild. Don't just set something to invisible and expect it to free up. Matt
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of shaun Sent: Monday, March 05, 2007 10:20 PM To: [email protected] Subject: Re: [flexcoders] Flex Player 9's (Flex 2) Memory Usage - What's Normal? Matt Chotin wrote: > Funny you bring this up, it came up in a separate discussion today. We > don't have a "typical" memory usage for a Flex app, it really depends on > what kind of work your application does. Do you load lots of images? > Those can take up space. How many components do you have, do you load > them in a deferred manner or all at once? One thing to remember is that > the Flash Player allocates memory in chunks, and it may not release > memory until enough has been allocated to force it to GC. So let's say > it allocated 40 megs. If the app happened to get to 33 megs there may > be no need for the Player to GC. And it could be that in reality the > Player could get away with only 20 megs, but it will take that whole 40 > b/c the OS is letting it and it. Still not technically a memory leak, > even if you think the task manager should show less. > > Remember to remove children from the display list. Remember to remove > event listeners or use weak listeners where appropriate. > Hmm, can you elaborate? Or is there a specific doc. I can read for some enlightenment on these? I don't know what weak listeners are or when I would need/want to remove children from the display list. cheers, - shaun
