JDK-8240556 : Abort concurrent mark after effective eager reclamation of humongous objects
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 15
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-03-05
  • Updated: 2021-04-30
  • Resolved: 2020-09-25
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 b18Fixed
Related Reports
Blocks :  
Blocks :  
Blocks :  
Blocks :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
Sometimes humongous allocations could trigger excessive concurrent mark cycles, although young-gen collections already reclaim many humongous objects with eager reclamation.
G1 could abort such unnecessary concurrent mark cycles in such cases.

See discussions in:
http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/2020-January/028357.html
http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/2020-March/028712.html
Comments
Changeset: 37b70282 Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2020-09-25 07:11:55 +0000 URL: https://git.openjdk.java.net/jdk/commit/37b70282
25-09-2020