JDK-6940674 : Progressively step down default heap size reservation request until OS can satisfy it
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 7
  • Priority: P4
  • Status: Resolved
  • Resolution: Withdrawn
  • OS: generic
  • CPU: generic
  • Submitted: 2010-04-02
  • Updated: 2015-11-11
  • Resolved: 2015-11-11
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
9Resolved
Related Reports
Relates :  
JDK-6315074 - Allow for an unbounded maximum heap size
Relates :  
JDK-4774036 - Java 1.4.x and virtual memory limits
Description
Heap size ergonomics can generate a virtual memory reservation size request that exceeds
what the OS can satisfy.  This is a particular problem on Windows when running a jvm embedded in another process.  It can be impossible to allocate a contiguous chunk of
virtual address space for the Java heap due to a fragmented virtual address space.

The current behavior is to refuse to start the vm.  In the absence of a non-contiguous
heap solution, an interim fix is to progressively step down the size of the heap
reservation request until the OS can satisfy it.  We probably want to stop at the
default minimum size, currently 96mb.
Comments
I think this feature would lead to much confusion on the part of users who have chosen 1 heap size but are getting another.
11-11-2015
ILW => MLM => P4 Impact: Medium, VM refuses to start. Not high since no data loss. Likelihood: Low, environment needs to be in a state that will trigger ergonomics to choose a large heap but not being able to satisfy it. Workaround: Medium, should be possible to provide specific arguments to the VM disabling the ergonomics.
30-01-2014