JDK-6215549 : Windows: AWT_Component/Automated/ComponentLeakTest fails
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2005-01-10
  • Updated: 2011-01-19
  • Resolved: 2005-03-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6Resolved
Related Reports
Duplicate :  
JDK-6240100 - PIT:Reg testcase awt/Component/ComponentLeakTest/ComponentLeakTest.html fails from mustang b24
Relates :  
JDK-6174747 - awt/src/AWT_Component/Automated/ComponentLeakTest
Description
The SQE test AWT_Component/Automated/ComponentLeakTest still fails on Windows platform. This happens from mustang b05.

The testcase message:
java.lang.RuntimeException: Frame not finalized
	at ComponentLeakTest.start(ComponentLeakTest.java:128)
	at com.sun.javatest.regtest.AppletWrapper$AppletThread.run(AppletWrapper.java:58)
	at java.lang.Thread.run(Thread.java:595)

The bug fix for 6174747 awt/src/AWT_Component/Automated/ComponentLeakTest was integrated in b15 and looks like it fixed the bug only on Solaris and Linux platforms.
###@###.### 2005-1-10 06:17:13 GMT
Comments
EVALUATION failed with mustang starting from b04 because of other reasons besides coalesceMap keys in Component. Possibly connected with JCK-hangs(#6189690). ###@###.### 2005-1-11 11:51:35 GMT I've reduced the test and it contains a Frame and a Window. According to hprof there is no any leaks in this application but test still fails because there is no garantees that finalize method invokes in application timelife. ###@###.### 2005-2-01 16:53:34 GMT I changed the test in the following way: I'm adding a WeakReferences on a Frame and a Window from this test. Then I invoke System.gc() and System.runFinalization() several times. finalize methods are not calling sometimes and WeakReference.get() returns not null just before test ends. Seems that the Frame and Window were not GC'ed and finalize methods was not invoke. ###@###.### 2005-2-08 13:50:20 GMT Tiger also has this bug. I just run it with old workspace and test found unfinalized frame in it. So it seems that results of using old jvm.dll with latest library has no reasons since this bug exist from tiger at least. ###@###.### 2005-2-08 14:52:11 GMT
10-01-2005