JDK-8204169 : Humongous continues region remembered set states do not match the one from the corresponding humongous start region
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-05-31
  • Updated: 2018-06-26
  • Resolved: 2018-06-14
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 11
11 b19Fixed
Related Reports
Relates :  
JDK-8203848 - Missing remembered set entry in j.l.ref.references after JDK-8203028
Relates :  
JDK-8205426 - Humongous continues remembered set does not match humongous start region one after Remark
Description
When deciding that a given humongous starts region remembered set should be dropped because we never reclaim it (because of large remembered set), the humongous continues region remembered sets are not updated.

There is no real issue with that as HC remembered sets are always empty, just annoying to look at in the logs, so I am filing this as an RFE.

Occurs eg. with gc/g1/TestEagerReclaimHumongousRegionsClearMarkBits.