Name: yyT116575 Date: 10/22/2001


java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)

When there is only one JInternalFrame attached to a JDesktopPane and that frame
is closed, the DesktopManager still maintains a reference to the closed (and
disposed) frame in the currentActiveFrame variable. Since the frame has been
closed and disposed, the DesktopManager should not maintain a reference to the
frame. By keeping the reference, garbage collection of the frame is delayed
until another frame is assigned to the DesktopManager's currentActiveFrame
variable, thus releasing the erroneous JInternalFrame reference.

This is a problem when attempting to analyze memory usage and potential memory
leaks because it is difficult to determine if there are any dangling object
references associated with the closed frame. Because garbage collection doesn't
occur until a new JInternalFrame is open, it is difficult to determine which
object references were not collected from the first frame and which object
references are valid as part of the new frame.
(Review ID: 134092)
======================================================================