Hello, I was wondering if anyone has run across memory consumption issues when using some of the eye candy in the Flex framework.
Here are a couple of examples of what I am referring to: 1. The translucent overlay on the rest of the app when using Alert.show in modal mode. (vs. using the flag Alert.NONMODAL) 2. Using <mx:WipeUp/> and <mx:WipeDown/> for the inEffect and outEffect of a component. I've been tracking the effect of using these effects by watching Task Manager|Mem Usage for the firefox.exe process right before and right after these effects run. We're talking 4-10MB of memory consumed each time these effects are run. (I know because I've done the process of tracking with the same code and the effects turned off resulting in 300KB-1.5MB). My concern is that: 1. I can't programmatically (minus the unsupported tip given to us by gskinner http://www.gskinner.com/blog/archives/2006/08/as3_resource_ma_2.html) force the Garbage Collector to run. 2. Since I can't force the Garbage Collector to run, the comments by Ted Patrick on Flash Player memory management and releasing memory back to the OS is highly concerning. (http://tech.groups.yahoo.com/group/flexcoders/message/48219 | http://tech.groups.yahoo.com/group/flexcoders/message/48330) I understand that effects would consume memory to run, but I don't like thinking that once the memory has been allocated I have no control on if it will be given back to the Operating System. I've tried leaving my app open all night to see if the memory allocation would go down and it doesn't. (You would think since the effects were long done it would) Also, the app I'm working on is one that needs to run all day, so closing and reopening the browser is not an option. Has anyone noticed what I've noticed or have any insight on how to use effects without increasing the footprint so? -Jun
