JDK-8371635 : G1: Young gen allocations should never be considered when comparing against IHOP threshold
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-11-11
  • Updated: 2025-11-24
  • Resolved: 2025-11-13
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 26
26 b25Fixed
Related Reports
Relates :  
Description
After young gc (and potentially somewhere else) G1 uses the recent allocation that led to that GC to determine whether to start a concurrent mark either now or later.

However, some/most of these allocations will go into young gen, which IHOP calculation should not consider. Only known allocations into old (e.g. humongous) should be used for this calculation.

Pointed out by [~iwalulya] during review of another issue.
Comments
Changeset: 7d78818a Branch: master Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2025-11-13 13:55:25 +0000 URL: https://git.openjdk.org/jdk/commit/7d78818ae609461ab830c32c222f15f1cab0d2d4
13-11-2025

A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/28175 Date: 2025-11-06 10:33:46 +0000
11-11-2025