Hello I'm dealing with memory issues myself. For a more in depth description of how resources are managed and even hacks to force garbage collection the venerable Grant Skinner did a 3 part series complete with interactive demos. Can't ask for much more than that!
http://www.gskinner.com/blog/archives/2006/06/as3_resource_ma.html Good luck and if anyone is interested I'm going to start on a component that views the System.totalMemory on a timer. Sort of a mini task manager. I'll post it on RIAForge or onflex.org when it's of any use. - paul --- In [email protected], "Kenneth Sutherland" <[EMAIL PROTECTED]> wrote: > > Thanks for the information, but it would be handy if there was some sort > of in depth tutorial on this. I've seen a couple of macromedia > presentations on various flex topics and found them useful, and one of > them mentioned in passing memory issues (but only for about 30 seconds). > If there was one that was specifically on memory issues, weak bindings > etc then that would be great. If such a presentation doesn't exist then > I'd recommend to macromedia that they create one. It's all very well > creating nice flashy web apps, but if they end up slowing down the host > machine after a few minutes of use due to sloppy weak code then that's > no use. > > There does seem to be a lack of in-depth books/information at the > moment. I've had a look at "Flex 2 training from the source" and it's a > bit fluffy and lacking any depth. Good book in that it covers the > basics but that's all it does. > > > > So although the updated photoviewer code will probably solve my issue > when I get to compare my code with the new code, I'd like to be able to > solve it myself by learning more about weak references and debugging the > app so that I can find the memory leak myself. > > > > Cheers Kenneth. > > > > > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Matt Chotin > Sent: 08 December 2006 05:33 > To: [email protected] > Subject: RE: [flexcoders] memory issues / garbage collection? > > > > 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. >
