JDK-6631680 : REGRESSION: api/java_awt/Container/index.html#isAncestorOf[Container2019] hangs up
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: OpenJDK6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86
  • Submitted: 2007-11-19
  • Updated: 2012-03-22
  • Resolved: 2007-11-20
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 7
7Resolved
Related Reports
Duplicate :  
Relates :  
Description
JCK: JCK-runtime-6b alt
J2SE: FAIL - JDK7b24, JDK6-Open-b01, JDK6-Open-b02
      PASSES - JDK1.5.0u14, JDK1.6.0u3
Platform[s]: FAIL -  Solaris-SPARC, WindowsXP, Linux

The following test:
api/java_awt/Container/index.html#isAncestorOf[Container2019]
takes unmeasurable amount of time to work - more than 6 hours and still gives no results.

The essence of the test that causes hanging is the following:

---------------------------------------------------------------
  final int NUMBER_OF_CONTAINERS = 50;
  Container[] containers = new Container[NUMBER_OF_CONTAINERS];
  containers[0] = new Container();
  for (int i = 1; i < containers.length; i++) {
      containers[i] = new Container();
      containers[i - 1].add( containers[i] );
  }
---------------------------------------------------------------

Number of 50 is critical, with 30 containers this code works fine.
For JDKs 1.5.0u14/1.6.0u3 it's a matter of seconds to go through all 50 containers.

Comments
EVALUATION the problem is introduced by refactoring made as part of fix for 6567564
20-11-2007