During my research with Flex performance found that instances of
WeakMethodClosure constantly increasing. I do not have knowledge what
is that and how to avoid it. 1859 instances for example can take only
30k of memory... but still
BTW found that Flash player running under Firefox & Opera newer fr
O, thank you! What about array.length = 0;?
Returning to WeakMethodClosure - in 1 hour of running application
profiller has 5600 instances of this thing, take 90kb of memory.
Examinig backreference shhows that many of them is adding events
listener inside components like charts. Are this valid
I imagine it's the internal voodoo to keep track of closures. Think of them
as function pointers which contain the creator's stack - that's a simplified
but useful view.
-J
On Wed, Mar 12, 2008 at 8:32 AM, lytvynyuk <[EMAIL PROTECTED]> wrote:
> During my research with Flex performance found th
Donald
Sent: Tuesday, March 11, 2008 3:54 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] WeakMethodClosure - what is this ?
I imagine it's the internal voodoo to keep track of closures. Think of
them as function pointers which contain the creator's stack - that's a
simp
rom: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of lytvynyuk
Sent: Friday, March 14, 2008 9:14 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] WeakMethodClosure - what is this ?
O, thank you! What about array.length = 0;?
Returning to WeakMethodClosure - in 1 hour of runn
5 matches
Mail list logo
