JDK-8276107 : Preventive collections trigger before maxing out heap
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 18
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-10-28
  • Updated: 2021-11-01
  • Resolved: 2021-11-01
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 18
18 masterFixed
Related Reports
Relates :  
Description
Preventive collections trigger before maxing out heap, i.e. it uses the current heap size for triggering instead of the maximum available.

As this feature is about preventing evacuation failures, they will not occur anyway if G1 can still expand the heap.
Comments
Changeset: e265f838 Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2021-11-01 16:48:13 +0000 URL: https://git.openjdk.java.net/jdk/commit/e265f83858b84451258677f130f98be5375a417a
01-11-2021