3 Replies Latest reply on Apr 7, 2010 11:30 AM by Flex harUI

    Troubleshooting memory leak

    tehxike1 Level 1

      I've spent about 4 hours now trying to figure this out...  I have a Popup that's been removed using PopupManager.removePopup(..) but is still lingering around.  Using the profiler, I've found that it has 4 Object Reference Paths:

       

      1) Popup > Class (focusedContainer) > Object (ContainerGlobals)

      2) Popup > PopupSkin > TextInputSkin > RichEditableText > CSSTextLayoutFormat > Dictionary > Class (computedFormatCache) > Object (HostFormatHelper)

      3) Popup > PopupSkin > Label > Dictionary > Class (cachedFontsForObjects) > Object (IEmbeddedFontRegistry) > Class (classMap) > Object (Singleton)

      4) Popup > PopupSkin > Label > Dictionary > Class (cachedFontsForObjects) > Object (EmbeddedFontRegistry)

       

      Why would any of these keep my popup from going away?  I can force the garbage collector to run, and it's still around.  Any help would be appreciated- I have no idea what to do next to troubleshoot this.

       

      Before someone links me to them, yes, I have read:

      * http://help.adobe.com/en_US/Flex/4.0/UsingFlashBuilder/WS6f97d7caa66ef6eb1e63e3d11b6c4d016 9-7ff6.html

      * http://www.adobe.com/devnet/flex/articles/flashbuilder4_debugging_profiling_03.html