Bug ID: JDK-6240100 PIT:Reg testcase awt/Component/ComponentLeakTest/ComponentLeakTest.html fails from mustang b24

JDK-6240100 : PIT:Reg testcase awt/Component/ComponentLeakTest/ComponentLeakTest.html fails from mustang b24

Type: Bug
Component: client-libs
Sub-Component: java.awt
Affected Version: 6

Priority: P2
Status: Closed
Resolution: Fixed
OS: generic,windows_xp
CPU: generic,x86

Submitted: 2005-03-14
Updated: 2011-01-19
Resolved: 2005-07-12

Versions (Unresolved/Resolved/Fixed)

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
6 b43Fixed

Related Reports

Duplicate :	JDK-6215549 - Windows: AWT_Component/Automated/ComponentLeakTest fails
Relates :	JDK-6245243 - CTE_REGTEST/Generic/4343272/MiniGnip.java fails
Relates :	JDK-6360792 - Regression: test ComponentLeakTest fails with 1.4.2_11b01 but passes with 1.4.2_10FCS
Relates :	JDK-4649647 - JFrame instances are not garbage collected upon disposal
Relates :	JDK-6282030 - Regression: CTE_REGTEST/Generic/4506928/Application.java fails
Relates :	JDK-6218115 - JFrame is not garbage collected in minor collection if JPopupMenu is displayed

Description

The regression testcase awt/Component/ComponentLeakTest/ComponentLeakTest.html fails from b24 onwards on Linux and Solaris. It passed on b23. It was failing in WinXP due to 6215549.

The jtr file attached.
###@###.### 2005-03-14 14:05:27 GMT

Comments

SUGGESTED FIX exclude the test ###@###.### 2005-05-27 09:34:58 GMT

27-05-2005

EVALUATION Might be closed as a duplicate of another CR. 6215549 reproduces on any platform. This is not Linux or Solaris specific failure. It depends on timing. We suppose that this is a GC issue. ###@###.### 2005-03-14 15:03:40 GMT Actually this test might be corrected in the following way: use WeakReference to every Component and toplevel (Dialogs, Windows, Frames) from the test to check if they were GC'ed or not. Until now finalize() methods used for this purpose. Finalizers may not be called at all while java application alive so they should not be used. ###@###.### 2005-05-24 13:26:08 GMT The test is still fails if WeakRefs are used. Seems that GC still doesn't clear heap area. ###@###.### 2005-05-24 15:55:38 GMT The only way of resolving this issue is to exclude the test from suite. ###@###.### 2005-05-27 09:34:58 GMT

14-03-2005