Title: Flex memory issues.

Can you break the large app into smaller apps that are loaded with Loader?

 

Have you used the profiler to see if there’s a method that’s being called maybe too often and creating objects that are never let go?  The profiler won’t give you memory information, but you could see if something is happening more than expected at least.

 

Matt

 


From: Mercer, Dustin [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 24,2005 4:11 PM
To: [EMAIL PROTECTED]
Subject: [flexcoders] Flex memory issues.

 

I have a very large flex app I am running into some random crashes and heavy memory consumption.  Memory consumption on Standard Flash Player (not Flash Debug Player) has been reaching 150 to 170 megs.  I need to know what I can do to manage this.  I have seen some methods available to the UIObject, mainly destroyObject, and I got this to remove objects that were no longer needed, but I cannot find a good way to re-instantiate them when they are needed again.  This could be a really bad approach, but I am afraid I may be pushing some limits on Flex that is forcing me down this route.  I am open to any suggestions.  If any more information is needed, I would be happy to provide.  Thanks in advance!

Dustin Mercer



Reply via email to