Thanks for your replies :) After doing some investigations and tests, i arrive to these results:
Test: Browsing 10 pictures (+/- 400Kb/pic) With flex 3: ---------------- - System.totalMemory = 20Mb - Task manager (IE7) = Stabilized around 94Mb With flex 2.0.1: ---------------- - System.totalMemory = 19Mb - Task manager (IE7) = Stabilized around 165Mb The only difference between both versions is thats i'm calling the System.gc() every 10 seconds with the flex3 version. So i'm feeling better now, i was scared that i would have to recreate all these image-intensive modules, fortunately that won't be necessary! Damien --- In [email protected], "Eric Cancil" <[EMAIL PROTECTED]> wrote: > > Also, if youre using even listeners make sure you clean those up / use weak > references. This issue can most likely be significantly tamed with some due > diligence on your behalf > > On Feb 8, 2008 10:29 PM, Gaurav Jain <[EMAIL PROTECTED]> wrote: > > > Hi Damien, > > > > High memory usage doesn't necessarily mean memory is leaking. You can > > use the profiler in Flex Builder 3 and investigate if the memory is > > getting reclaimed or not. If you find the memory is leaking, you can > > use the object references panel to investigate why the objects are not > > getting GCed. > > > > Profiler in FB3 can be used even if swf is compiled with Flex 2.0.1 > > (as long as it is compiled in debug mode). > > > > Also before the load() method, you may try the following: > > > > imgPic.source = ""; > > > > Thanks, > > Gaurav > > > > --- In [email protected] <flexcoders%40yahoogroups.com>, "Damien > > Legros" <damien.legros@> > > > > wrote: > > > > > > Hi there! > > > > > > We are in the last development step of our new cms product. We > > > developed it with flex (2.0.1) and it is time to improve its > > > performances a little bit ;) > > > > > > When used intensively we noticed an abnormal memory usage (over 1Gb in > > > both IE7 and FF). > > > The memory leak has been located in our code near the mx:Image loading > > > procedures. > > > > > > > > > > > > Basically, we have a "picture viewer", with next/previous buttons etc. > > > The loading code looks like that: > > > > > > var url:String = ....; > > > imgPic.load(url + "/" + _listPics[_curPic]); > > > > > > And the Image component: > > > > > > <mx:Image id="imgPic" autoLoad="false" scaleContent="false" > > > completeEffect="{effFade}" /> > > > > > > > > > > > > After some researches, it seems that this is a known issue, so my > > > question is: will it be fixed in flex 3 or/and is there a "hack" to > > > prevent this memory leak? > > > > > > Thanks in advance, > > > Damien > > > > > > > > > >
