Hello,
 
I've checked the archived email and saw some people having the same questions in regards with the way garbage collector works. Unfortunately, I wasn't able to find anything that would help. Is there anyone out here that know how the GC works and what we need to know to avoid memory leaking... For example I'm not sure that loading/unloading am mxml via mx:Loader will ever free up the memory or will continue to add on top of the used memory......
 
I have the same question for view stacks...For a large app is it safe to group multiple screens under the same view stack or using separates applications would be the way to go....
 
 
Thanks for your patience,
Valy


Manish Jethani <[EMAIL PROTECTED]> wrote:
On 5/10/05, Valy Sivec <[EMAIL PROTECTED]> wrote:

> 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);
>
> }

I doubt that (not that I have any suggestions).  Check out these threads:
http://www.mail-archive.com/[email protected]/msg04331.html
http://www.mail-archive.com/[email protected]/msg04462.html


Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.

Yahoo! Groups Links

Reply via email to