That is correct, and the profiler occasionally shows them as leaking when they're really not. I typically examine them to see if they have valid backreferences. If they do, they should be investigated. If they don't have back references, then I don't worry about them.
There is an open issue with the Flash Player where several browsers show process memory continually increasing even though System.totalMemory is not. My observation is that minimizing the browser and restoring it frees up that memory. I haven't proven either way whether the browser would have released that memory before running out of memory. Generally, I would only be concerned about System.totalMemory, especially if the minimize/restore trick frees up the process memory. ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald 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 simplified but useful view. -J On Wed, Mar 12, 2008 at 8:32 AM, lytvynyuk <[EMAIL PROTECTED] <mailto:[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] <mailto:[EMAIL PROTECTED]>
