JDK-8248917 : G1: Reconsider counting aborted concurrent marks as full collections
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 16
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2020-07-07
  • Updated: 2020-07-10
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8240556 - Abort concurrent mark after effective eager reclamation of humongous objects
Description
Currently any started concurrent mark is counted as a complete full collection even if it has actually been aborted for one reason or another.

Reconsider whether this makes sense particular wrt to JDK-8240556.

That is, we might report tons of concurrent cycles where a significant amount has been aborted and actually done nothing.