Re: [flexcoders] mx;Loader/ memory leaking/ any way to programatically clear the memory/browser crashes

Tue, 10 May 2005 06:45:46 -0700

Hello,
 
I'm experiencing odd behaviour from a flex app that uses mx:Loader to load some views. Under heavy load, loading/unloading a mxml file via mx:Loader puts the browser on his knees and finally crashes without logging anything in the log. I've monitored the RAM usage by the IE process and it looks that memory usage raise around 50Mb and then the browser dies...
 
I'm wondering if adding this code on the "unload" event will help cleaning the memory....because I'm suspecting some memory leaking...
 

var source = event.target;

for( i: Number = 0; i< source.numChildren; i++ ){

source.destroyChildrenAt(i);

}

 

Any suggestions would be helpfull.

Valy



Valy Sivec <[EMAIL PROTECTED]> wrote:

Hi Flex gurus,

I have this scenario: left page navigation with dynamic filter criteria and in the main screen I load sub-views via mx:loader tag. The user can make some real-time selections from the left page and as result I'll display on the right screen a different view via mx:Loader tag. Everything works fine, but from time to time the browser crashes... totally random, without being able to find a pattern in this behavior other than playing with the left navigation that load/re-load the right screen.... I'm wondering if the mx:Loader tag causes some memory leaking and if there is anything that I should know about it... I search the archive for some hints but no luck....

Any suggestions are welcome...

Valy

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
Yahoo! Groups Links

Reply via email to