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 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 free > memory. Even when profiler shows clear memory dis-allocation. > > > -- "Therefore, send not to know For whom the bell tolls, It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
