Flex memory issues.
Title: Flex memory issues. I have avery 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. Thanksin advance! Dustin Mercer
RE: [flexcoders] Flex memory issues.
Title: Flex memory issues. Upon more investigation, my memory usage seems to be stemming from my higher resolution. When I run the app in 1024*768 the memory consumption does not seem to exceed 110mb (high, but manageable for the size of this app). When run in 1280*1024, them memory usage is increased by 50mb or so. It looks like this is an issue with the graphics the controls are rendering. Makes sense. Maybe I can get some help with some good ideas on how to better manage this. Does anyone know how to enable the Flash quality setting in Flex. I want to try to turn the quality down to see what kind of memory results I get with that. I remember seeing an article like this, just cant seem to find it. Thanks! Dustin Mercer From: Mercer, Dustin 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
RE: [flexcoders] Flex memory issues.
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 theres a method thats being called maybe too often and creating objects that are never let go? The profiler wont 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
RE: [flexcoders] Flex memory issues.
Title: Flex memory issues. Unfortunately I havent had the opportunity to do any profiling yet. I tried it a couple of weeks ago, couldnt get it to work and I had to get back to developing the application. I will set aside some time to do this though. To the other suggestion, I havent experimented with the loader component to break up the app. Good Idea and I will explore this option though. One concern I have about this is: If I break these components down, can I still communicate easily between them and can I stop people from accessing those new apps directly? I have some needs to do this. Plus, I would like some of them to keep state. My first option seems to be some profiling though. I will try to get this working as soon as possible. Thanks for the response! From: Matt Chotin [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24,2005 10:18 PM To: [EMAIL PROTECTED] Subject: RE: [flexcoders] 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 theres a method thats being called maybe too often and creating objects that are never let go? The profiler wont give you memory information, but you could see if something is happening more than expectedat 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
RE: [flexcoders] Flex memory issues.
Title: Flex memory issues. Not sure if MovieClip._quality makes a difference in Flex: http://livedocs.macromedia.com/flash/mx2004/main_7_2/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Flash_MX_2004file=1548.html My guess is that youll need the default (HIGH) since your app probably has text in it and the docs say text depreciates in MEDIUM. Matt From: Mercer, Dustin [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24,2005 6:02 PM To: [EMAIL PROTECTED] Subject: RE: [flexcoders] Flex memory issues. Upon more investigation, my memory usage seems to be stemming from my higher resolution. When I run the app in 1024*768 the memory consumption does not seem to exceed 110mb (high, but manageable for the size of this app). When run in 1280*1024, them memory usage is increased by 50mb or so. It looks like this is an issue withthe graphics the controls are rendering. Makes sense. Maybe I can get some help with some good ideas on how to better manage this. Does anyone know how to enable the Flash quality setting in Flex. I want to try to turn the quality down to see what kind of memory results I get with that. I remember seeing an article like this, just cant seem to find it. Thanks! Dustin Mercer From: Mercer, Dustin 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
