JDK-8342376 : More reliable OOM handling in ExceptionDuringDumpAtObjectsInitPhase test
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 17,21,23,24
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-10-16
  • Updated: 2024-10-21
  • Resolved: 2024-10-21
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 24
24 masterFixed
Related Reports
Blocks :  
Relates :  
Description
Found a test bug while testing JDK-8341913 with Shenandoah. The allocation that follows OOM almost always succeeds with Shenandoah. Actually, it succeeds with other GCs as well, it just so happens that other GCs throw OOM with "GC overhead limit exceeded".
Comments
Changeset: 37aa320f Branch: master Author: Aleksey Shipilev <shade@openjdk.org> Date: 2024-10-21 15:56:19 +0000 URL: https://git.openjdk.org/jdk/commit/37aa320f573650f007e60729e4d187c3b96b5756
21-10-2024

A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/21536 Date: 2024-10-16 11:51:50 +0000
16-10-2024