JDK-8204081 : Mismatch in rebuild policy and collection set chooser causes remembered sets to be kept errorneously
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-05-30
  • Updated: 2018-06-21
  • Resolved: 2018-06-07
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 b18Fixed
Related Reports
Relates :  
Relates :  
Description
A mismatch in the rebuild policy to select regions for remembered set rebuild and collection set chooser causes the latter to not clear out remembered sets for some old gen regions.

I.e. the rebuild policy basically only selects by liveness, but the collection set chooser selects and discards only regions which marking were updated.

This makes regions that were allocated during marking, that were selected for rebuild during remark (because e.g. due to fragmentation they were "half-empty"), to not be part of the set of regions to be looked at in the collection set chooser, and hence their remembered set not cleared out if applicable.

This is a memory/performance issue as these regions keep being maintained for longer than necessary.