Name: moC74494 Date: 06/04/98
I am experiencing a problem where the LightweightDispatcher created on behalf og my Container continues to maintain a reference to the Container in the LightweightDispatcher.nativeContainer field even after I have removed the Container from its parent Container. I have perused the Container source code and do not see where this reference is ever cleared.
This bug is preventing my applet from successfully removing itself from the VM. Instead, I leave several dangling references. Is there any
(Review ID: 29065)
IHAC that is experiencing this same issue as above. If you compile and
run the testcase in the attachments you can see the behavior. This
behavior is more noticable when running the testcase thru OptimizeIt
an Application that monitors class references, memory, etc..
In OptimizeIt you can see that LightweightDispatcher keeps a reference
to AppletRepaint that is the applet that is continously being redrawn.
These references are probably keeping the instances from being GCed.
Because before a new applet is created the old one is stopped, destroyed
and removed from the frame so it has no reference.
To run the testcase compile all the java files in the attachments and type:
java TestApplet gc
from there you will see a gradual memory leak. There is unfortunately
no way to incorporate the information from OptimizeIt in this bug. If you
need this information let me know.