Use the profiler to check for memory leaks. If you don't see any obvious ones, then export a release build and use a release player and watch memory with ProcessMonitor. There's been reports that debuggable modules do not completely unload, especially in FP9
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Guy Morton Sent: Wednesday, November 19, 2008 12:44 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Memory Leaks... Cumulative Memory and Memory. I'm interested in knowing more about this too...I have an app that seems to cause the browser's memory to increase steadily over the course of several hours. However, if I run WSMonitor alongside it, it says the memory usage of my app *doesn't* increase overall (though it fluctuates between 130 and 150mb - it loads data continuously so this is expected). http://www.websector.de/blog/2007/10/01/detecting-memory-leaks-in-flash-or-flex-applications-using-wsmonitor/ So my question is, should I trust WSMonitor? Or is the browser right and I have a memory leak? This has been observed in Firefox on Mac OS, as well as Chrome and FF on Windows. Guy On 20/11/2008, at 7:29 AM, sailors! ea21 wrote: Hi everyone, I think I'm having some issues with memory leaks. The memory of my Cumulative Memory and of my Memory keep increasing. When I unload modules, the memory doesn't drop and if I reload the modules, the memory keeps climbing... When I use the import command (ie:import mx.controls.Alert;), do I need to unload the "mx.! controls.Alert" when I unload my module? If so, how do! I do th is? If not, why does my memory keep climbing when I unload a module and reload it? Shouldn't it drop and then climb back? Thanks. -David
