I'm completely guessing here, but could it be that your modules are including framework classes that aren't linked into the main application? That might keep the module from being collected because the VM wants to keep the classdefs around?
-Josh On Fri, Sep 19, 2008 at 10:34 AM, 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 > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." http://flex.joshmcdonald.info/ :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
