JDK-7038914 : VM could throw uncaught OOME in ReferenceHandler thread
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 7u2
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-04-22
  • Updated: 2017-06-26
  • Resolved: 2013-07-03
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.
8Fixed 9Fixed
Related Reports
Relates :  
During stress test VM could get OOME in ReferenceHandler thread.

It happens only with G1 starting from JDK b138 HS 21 08.

At Twitter we are running OpenJDK regression tests with Graal and test/java/lang/ref/OOMEInReferenceHandler.java fails because it's using a heap size of 24MB. I wanted to see if the initial bug had anything to do with JIT compilations. I highly doubt it because the only compilations happening when running this test are java.base methods. Basically, I'd like to run that test with -Xint.

Unfortunately JDK-8016341 must remain confidential because it contains references to Oracle internal infrastructure. Chris, maybe you could be more specific about what you're looking for. If there's something relevant and non-confidential in that bug, maybe we can fish it out for you.

test/java/lang/ref/OOMEInReferenceHandler.java lists: @bug 7038914 8016341 which is: changeset: 7648:7bb17aa9a09f user: dholmes date: Tue Jul 09 22:01:57 2013 -0400 files: test/java/lang/ref/OOMEInReferenceHandler.java description: 8016341: java/lang/ref/OOMEInReferenceHandler.java failing intermittently Summary: Ensure WeakRef object can't be prematurely gc'd Reviewed-by: chegar, plevart but JDK-8016341 is not publicly visible. Could that be changed?

Testcase still causing issue (JDK-8022321)

There are no plans at this point to backport this to a jdk7u release so I'm closing this bug. Note that a backport issue type was used for the fix in 8.

The bug management for this CR got into a mess. I've converted this to an issue against 7u where the problem still exists. 8015434 is the JDK8 "backport" of this CR.

This is a jdk bug, and has been solved there. Since the fix version has not been changed, there is this 8015434 backport.

Duplicate of 8015434