I still haven't used Scout, but the Flash Builder Profiler has helped me track down many issues like this. It should show you what is referencing those old objects.
On 10/16/13 1:26 AM, "[email protected]" <[email protected]> wrote: >Hi, > >I am currently having Major Memory issues, which I haven't quite managed >to sort out. > >In my application (Apache Flex 4.10 ... but wasn't any different in older >and/or Adobe Versions) I am loading a list of objects and this list is >updated via server-push (Streaming AMF Connection). For testing, I >increased the amount of data sent back to the Client when loading the >list. Currently about 12000 Objects are returned using about 107MB >(according to Adobe Scout). > >The returned list of objects is displayed in a Flexicious Ultimate >DataGrid (The Performance of this is very sattisfying considering the >amount of data it has to handle). > >There is a Feature to force a reload of the list. As removing all >elements of an ArrayList and then adding 12000 Objects caused Major >Performance problems, I changed the code to replace the source array of >the ArrayCollection and then to make the list update itself after that. >Each time the list is reloaded 107MB are used but I can't see any Memory >being freed. > >Is there something wrong with my Approach? Do I have to Keep something >else in mind? Are there some hidden internals keeping a reference to my >objects so they aren't cleaned up? > >Help greatly appreciated. > >Chris
