Thanks Claudiu,
I'm using the ModelLocator as a storehouse for data providers, etc.
required by the Module. But as the ModelLocator is a singleton, and
would 'survive' the life of the module, that references to the module's
components from the data provider might prevent GC.
The scenario I observed was when the user logs out, all active modules
are unloaded, but when they log back in again, the memory consumption
just jumps right up. But you are right - I have embedded CSS in the
module! - That could be my smoking gun!
Jeff
-----Original Message-----
From: flexcoders@yahoogroups.com
[mailto:flexcod...@yahoogroups.com] On Behalf Of claudiu ursica
Sent: Tuesday, March 24, 2009 1:10 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Modules, Cairngorm and Garbage
Collection
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" <jeff.battersh...@dowjones.com>
To: flexcoders@yahoogroups.com
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
<mailto:jeff.battershall%40dowjones.com>
(609) 520-5637 (p)
(484) 477-9900 (c)
