JDK-8311215 : [BACKOUT] JDK-8047998 Abort the vm if MaxNewSize is not the same as NewSize when MaxHeapSize is the same as InitialHeapSize
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 22
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2023-07-01
  • Updated: 2023-11-11
  • Resolved: 2023-07-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 22
22 b05Fixed
Related Reports
Duplicate :  
Relates :  
Description
In order to reduce the noise in the JDK22 CI, I'm backing out the following fix:

JDK-8047998 Abort the vm if MaxNewSize is not the same as NewSize when MaxHeapSize is the same as InitialHeapSize

Two tests are failing many times in Tier2 after JDK-8047998: 

  10 gc/arguments/TestNewSizeFlags.java 
  10 gc/arguments/TestVerifyBeforeAndAfterGCFlags.java 

so 20 failures per Tier2. 

Three tests are failing many times in Tier3 after JDK-8047998: 

   4 compiler/runtime/Test8010927.java 
   6 jdk/jfr/event/gc/detailed/TestPromotionFailedEventWithDefNew.java 
   6 jdk/jfr/event/gc/detailed/TestPromotionFailedEventWithParallelScavenge.java 

so 16 failures per Tier3. 
Comments
Changeset: 0e3d91dc Author: Daniel D. Daugherty <dcubed@openjdk.org> Date: 2023-07-01 15:55:29 +0000 URL: https://git.openjdk.org/jdk/commit/0e3d91dc213b5173f72e954d9b8e13e1b8343b23
01-07-2023

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/14747 Date: 2023-07-01 13:57:02 +0000
01-07-2023