JDK-8370491 : Release Note: G1: Support UseGCOverheadLimit
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version:
    26,17.0.19-oracle,21.0.11-oracle,25.0.3-oracle,8u491-perf 26,17.0.19-oracle,21.0.11-oracle,25.0.3-oracle,8u491-perf
  • Priority: P4
  • Status: Resolved
  • Resolution: Delivered
  • Submitted: 2025-10-23
  • Updated: 2025-12-03
  • Resolved: 2025-11-06
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 17 JDK 21 JDK 25 JDK 26 JDK 8
17.0.19-oracleResolved 21.0.11-oracleResolved 25.0.3-oracleResolved 26Resolved 8u491-perfResolved
Description
The G1 garbage collector now throws an `OutOfMemoryException` when the garbage collection overhead is more than `GCTimeLimit` percent (default value `98`) and the free Java heap is less than `GCHeapFreeLimit` percent (default value `2`) for five consecutive garbage collections.

This feature is enabled by default. It can be disabled using the `-XX:-UseGCOverheadLimit` option. 

The implementation mirrors the functionality already provided by the Parallel garbage collector. However there may be differences in the exact conditions for the OOME triggers as G1 calculates garbage collection overhead and free Java heap slightly differently.