JDK-8141422 : G1 eager reclaim card dirtying may dirty outside of allocated objects
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-11-04
  • Updated: 2016-04-19
  • Resolved: 2015-11-04
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.
9 b94Fixed
Related Reports
Relates :  
A stale remembered set entry on a humongous region selected for eager reclaim may point to unallocated memory.
Previously a fix was applied to avoid dirtying cards which cover regions which are free but this fix is in fact insufficient, we also need to consider the case where a region is not full.
This can lead to verification failures in fastdebug builds.

Suggested fix is to change the check from "not is free" to "is in closed subset".