0 Replies Latest reply on Jan 27, 2009 5:15 AM by (Corey_Lucier)

    [svn] 4684: When a component instance was removed from the DOM, and it happened to have been recently in focus, there were several constructs in Flex that were pinning the instance in memory , preventing the player from GC'ing it.

    Level 1
      Revision: 4684
      Author: clucier@adobe.com
      Date: 2009-01-27 05:15:31 -0800 (Tue, 27 Jan 2009)

      Log Message:
      -----------
      When a component instance was removed from the DOM, and it happened to have been recently in focus, there were several constructs in Flex that were pinning the instance in memory, preventing the player from GC'ing it. Namely, the HaloFocusRect and the focusableCandidates array within the FocusManager.
      Reviewer: Alex, Darrell
      Doc Notes: None
      Bug Notes: Related to SDK-14781 and the three duplicates (SDK-18717, SDK-18755, SDK-18575), note this is not a comlete fix as there is one outstanding player issue logged (2267790).

      Ticket Links:
      ------------
      http://bugs.adobe.com/jira/browse/SDK-14781
      http://bugs.adobe.com/jira/browse/SDK-18717
      http://bugs.adobe.com/jira/browse/SDK-18755
      http://bugs.adobe.com/jira/browse/SDK-18575

      Modified Paths:
      --------------
      flex/sdk/branches/3.3.0/frameworks/projects/framework/src/mx/core/UIComponent.as
      flex/sdk/branches/3.3.0/frameworks/projects/framework/src/mx/managers/FocusManager.as
      flex/sdk/branches/3.3.0/frameworks/projects/framework/src/mx/skins/halo/HaloFocusRect.as