Actually I forgot, there was a memory leak still found due to an event listener. We've fixed it in the 2.0.1 version of the sample (I didn't do it, the bug note said we made an event listener weak to address it). So it was my fault :-)
Matt ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Chotin Sent: Thursday, December 07, 2006 9:23 PM To: [email protected] Subject: RE: [flexcoders] memory issues / garbage collection? When we wrote the PhotoViewer there were some memory leaks but I thought we got them all. If you keep an eye on the task manager it should go back down after a minute or two. Of course if by "playing with the app" you mean you edited it, I absolve myself of responsibility, even if all you did was change a color ;-) Matt ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Sent: Thursday, December 07, 2006 12:20 PM To: [email protected] Subject: RE: [flexcoders] memory issues / garbage collection? I was having this problem when I built the map component for www.pikeo.com <http://www.pikeo.com/> You have to make sure that all references to an object are gone before it will get garbage collected. Once all references to the object are gone it will get collected within 5 seconds usually. --Kelly ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Sutherland Sent: Thursday, December 07, 2006 1:18 AM To: [email protected] Subject: [flexcoders] memory issues / garbage collection? I've been playing around with the photoviewer example (from the adobe site) quite a bit in my spare time and I've noticed that when I open up the taskmanager and I run the application that the memory consumption just keeps on going up! Each time I look at another photo, up it goes. So I'm looking for any hints, tips, tutorials or books that will help to get flex to garbage collect all of the old memory that the app no longer needs. Thanks.
