JDK-6566474 : PS: In the UseParallelGC collector the minimum gen0 size can exceed the maximum gen0 size.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS:
    generic,linux_ubuntu,solaris_10,windows_xp generic,linux_ubuntu,solaris_10,windows_xp
  • CPU: generic,x86,sparc
  • Submitted: 2007-06-06
  • Updated: 2012-03-26
  • Resolved: 2007-06-20
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
6u4Fixed 7Fixed hs10Fixed
Related Reports
Relates :  
JDK-6527727 - Sizing parameters: Sole starting/minimum spec should bound default choice of maximum from below
Relates :  
JDK-6524727 - GC ergonomics does not honor the minimum young gen size implied by a -Xms and NewRatio
Description
Internal Error at adjoiningGenerations.cpp:48, pid=10612, tid=2
Error: assert(min_high_byte_size <= init_high_byte_size && init_high_byte_size <= max_high_byte_size,"Parameter check")

The bug was introduced in b13 with the fix for 6524727.
Comments
SUGGESTED FIX http://prt-web.sfbay.sun.com/net/prt-archiver.sfbay/data/archived_workspaces/main/gc_baseline/2007/20070608185726.jmasa.gc_baseline_6566474/workspace/webrevs/webrev-2007.06.08/index.html
15-06-2007
EVALUATION When the minimum size for gen0 is calculated from NewRatio, the resulting value needs to be checked against MaxNewSize.
06-06-2007