JDK-8073463 : G1 does not mangle freed heap regions
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-02-19
  • Updated: 2015-06-03
  • Resolved: 2015-03-13
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 b59Fixed
Related Reports
Relates :  
In the call to HeapRegion::hr_clear from G1CollectedHeap::free_region, true is passed for the argument "clear_space", but the region does not become mangled. There is a call to G1OffsetTableContigSpace::clear, but it does not seem to work.
ILW = Low (makes debugging harder but don't affect product), High (always), High (none) = P4

Intentionally guarded by ZapUnusedHeapArea which is only true in debug builds and not available in other builds. This is not specific to G1 either (look in Space::clear())