JDK-8369111 : G1: Determining the concurrent start uses inconsistent predicates
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 26
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2025-10-03
  • Updated: 2025-10-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.
JDK 26
26Unresolved
Related Reports
Causes :  
JDK-8238687 - Investigate memory uncommit during young collections in G1
Description
G1 only uses the next allocation size in a few cases to determine whether the next gc should be a marking. This unnecessarily delays marking/causing instability in the test shown in JDK-8368959.

It had been introduced in JDK-8238687 in some cases, but forgotten in others.