The GC is not called when the component is remove from the screen. Most people think this occurs, but it's not truth.
The GC is called when its required, but WHEN it is required is another point. If you are using just a small piece of your available mamory, don't expect the GC to be called. Regards, PS On Tue, Mar 24, 2009 at 2:09 PM, claudiu ursica <[email protected]>wrote: > Hi, why do you bind module to the model locator? > > If by any chance you have embedded CSS in the module it won't garbage > collect ... > > Claudiu > > ------------------------------ > *From:* "Battershall, Jeff" <[email protected]> > *To:* [email protected] > *Sent:* Tuesday, March 24, 2009 5:37:58 PM > *Subject:* [flexcoders] Modules, Cairngorm and Garbage Collection > > I've been working on optimizing an AIR application I'm currently working > on that utilizes modules. In the modules there are controls bound to > ModelLocator data items. > > What I'm seeing during profiling that removing a module from the display > list doesn't seem to result in the module being GC'ed. I'm suspecting > binding between the ModelLocator and the module's controls are causing > the behavior. > > Has anyone seen this and can suggest approaches to address this? > > Jeff Battershall > Application Architect > Dow Jones Indexes > jeff.battershall@ dowjones. com <jeff.battershall%40dowjones.com> > (609) 520-5637 (p) > (484) 477-9900 (c) > > > -- /** * Pedro Sena * Systems Architect * Sun Certified Java Programmer * Sun Certified Web Component Developer */
