JDK-6672698 : mangle_unused_area() should not remangle the entire heap at each collection.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-03-07
  • Updated: 2010-05-09
  • Resolved: 2008-08-29
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 6 JDK 7 Other
6u14Fixed 7Fixed hs14Fixed
Related Reports
Relates :  
JDK-6672574 - parallel gc can no longer afford to scribble on memory with a single thread
Description
mangle_unused() writes a pattern into the unused part of the heap in debug mode.
If the heap is large, this can cause excessively long GC's to the point
that tests timeout.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/12eea04c8b06
10-07-2008
EVALUATION managle_unused_area() only mangles from top to end in a space. Set some artificial limit on the amount that will be mangled at each collection.
07-03-2008