Hi there, Yes I had read your post and a few others, and sat through a 1 hour demo on how to use the profiler before I started, all really good stuff and I am pretty sure I am using it correctly.
I loaded the app, opened and closed the window and I was taking a before and after snapshot and then checking for loitering objects. I had already discovered the "FocusManager reference" issue as well, and I remember to click out before running the after snapshot just to make sure it can be GC'd. Actually I figured out last night why the TextArea was not getting GC'd. It was the reference caused by the styleName property on the HaloBorder skin that causes the problem. I then made my own copy of HaloBorder and changed it so it did not store the styleName (which for skins is a ref to the parent component) and instead I used the parent property (which also points to the parent component) to "get" styles, and that worked and it got GC'd. So I am wondering whether that is the same issue with the other problem components. tks --- In [email protected], Alex Harui <[EMAIL PROTECTED]> wrote: > > I'm not aware of an problems like that. See my blog post on the profiler to make sure you're using it correctly. > > I've seen some issues that the last component to have focus pins that component until focus goes elsewhere. > > -Alex > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of reflexactions > Sent: Thursday, September 18, 2008 7:41 AM > To: [email protected] > Subject: [flexcoders] GC Issues > > > I have been working using the profiler for the last several days > trying to resolve some serious memory issues with our application. > > I am interested in hearing from others who have used the profiler and > if they are seeing the same issues as we are. > > Our application is mainly structured as a series of TitleWindow's > that each contain a Module. The problem has been Modules that don't > get GC'd. > > Of course we went after the obvious thing like making listener's use > weakReferences and generaly reviewing our code but when that didnt > resolve the problem we dug deeper. > > What we noticed was that certain controls seemed to prevent the > Module from being GC'd. > > In the end we tried a completely empty Module, just opening/closing > tags in mxml and then added simple tags without any attribute or > binding to complicate things. > > So we got to several VBox/HBox/Form/FormItem/Label and everything is > fine, you close and the Module is GC'd. > > But then the first "problem" control we hit was the TextArea. Add > that to the mix and the Module wont be GC'd, remove it and it does. > > Same with DataGrid. > > Same with any mxml component (even an empty mxml component) > > We are pretty surprised that basic framework control are causing > problems, we expected our own to cause issues or our bad code but not > framework controls. > > Anyone used the profiler and seen this sort of problem? > > tks >
