JDK-8147480 : Mark FJExceptionTableLeak.java as intermittently failing
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.concurrent
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-01-15
  • Updated: 2016-06-13
  • Resolved: 2016-01-15
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 9
9 b102Fixed
Related Reports
Relates :  
JDK-8144990 - java/util/concurrent/forkjoin/FJExceptionTableLeak.java: OOM with Xcomp,G1GC
Relates :  
JDK-8147508 - Correct fix for JDK-8147480
Description
The test

java/util/concurrent/forkjoin/FJExceptionTableLeak.java

intermittently fails at low-frequency (JDK-8144990). This fact should be marked in the test and the test demoted from tier 1 to tier 2 until the issue is resolved.
Comments
Review thread: http://mail.openjdk.java.net/pipermail/core-libs-dev/2016-January/038080.html
15-01-2016
I'm OK with this - pre-approved! If there are recommendations for how to write regression tests for java-level memory leaks, I'd like to see them. Testing for OOME is fragile. The best strategy seems to be using reflection to find the tree of objects retained by a java object, but I don't know of anyone doing that, and this is also brittle and unsatisfying.
15-01-2016