JDK-8129573 : CollectedHeap::fill_with_objects() needs to use multiple arrays in 32 bit mode too
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-06-23
  • Updated: 2015-09-10
  • Resolved: 2015-06-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 9
9 b74Fixed
Related Reports
Relates :  
JDK-8129558 - Coalesce dead objects during removal of self-forwarded pointers
Relates :  
JDK-8042668 - Provide GC support for shared heap ranges in Class Data Sharing
Description
In JDK-8042668 we introduced the use of CollectedHeap::fill_with_objects() with a custom maximum filler object size for G1.
That custom maximum filler object size is significantly lower than the 8G talked about in the comments of CollectedHeap::fill_with_objects(), so that even in 32 bit VMs it may happen that fill_with_objects() can be called with a size that is larger than that, requiring the use of multiple objects.

This issue can be reproduced with JDK-8129558 that also uses fill_with_objects() on GCBasher.
Comments
ILW = High (corrupted heap, potentially causing crashes), Low (never happened), Low (there is not really a workaround, but it did not occur yet at all)
23-06-2015