Ah, for anyone else curious, you have to take a memory snapshot before this will work
On Fri, Oct 23, 2009 at 3:06 PM, Alex Harui <aha...@adobe.com> wrote: > > > Double click on the object and it should show you all references to that > object. > > > > Alex Harui > > Flex SDK Developer > > Adobe Systems Inc. <http://www.adobe.com/> > > Blog: http://blogs.adobe.com/aharui > > > > *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On > Behalf Of *Jake Churchill > *Sent:* Friday, October 23, 2009 9:30 AM > *To:* flexcoders@yahoogroups.com > *Subject:* Re: [flexcoders] ArrayCollection of VO's Memory Leak?? > > > > > > Where do you go to see that? All I can see is the number of instances an > object has and the memory those instances take up? > > On Fri, Oct 23, 2009 at 1:10 AM, Alex Harui <aha...@adobe.com> wrote: > > > > The profiler should be able to show you who is still referencing the > objects. > > > > Alex Harui > > Flex SDK Developer > > Adobe Systems Inc. <http://www.adobe.com/> > > Blog: http://blogs.adobe.com/aharui > > > > *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On > Behalf Of *Jake Churchill > *Sent:* Thursday, October 22, 2009 10:57 AM > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] ArrayCollection of VO's Memory Leak?? > > > > > > Hi all, > > I have a charting application where I have an ArrayCollection of VO's. The > chart has several series, each looking at one property in the VO. > > There are several controls that when changed, require a re-calculation of > the VO's in the ArrayCollection. Before I do the re-calculation, I call > .removeAll() on the ArrayCollection and re-populate it with new VO's. > > When I run the profiler, my VO instances grow with each re-calculation. > So, why doesn't the garbage collector take care of the objects that got > removed from the ArrayCollection? How can I fix this? > > Please help. > > Thanks! > > -Jake > > > > >
