JDK-8253411 : [BACKOUT] [REDO] G1 incorrectly limiting young gen size when using the reserve can result in repeated full gcs
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 16
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-09-21
  • Updated: 2020-09-29
  • Resolved: 2020-09-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 16
16 b17Fixed
Related Reports
Blocks :  
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
Back out change  JDK-8244603 (re-introduced in JDK-8249676 after testing found no occurrences) again because it still triggers crashes in CI (e.g. JDK-8253295, JDK-8253389), although not as frequently as before.
Comments
Sightings of the following also increased: JDK-8248438 SIGSEGV in ObjectMonitor::enter from very rare to multiple sightings in same Tier7 and Tier8 CI job sets.
21-09-2020

Changeset: bba948f0 Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2020-09-21 11:29:41 +0000 URL: https://git.openjdk.java.net/jdk/commit/bba948f0
21-09-2020