Bug ID: JDK-7053840 Java heap is increased much beyond the -Xmx definition

Type: Bug
Component: hotspot
Sub-Component: runtime
Affected Version: 6u21

Priority: P2
Status: Closed
Resolution: Cannot Reproduce
OS: solaris_10
CPU: sparc

Submitted: 2011-06-12
Updated: 2012-05-02
Resolved: 2012-01-24

Versions (Unresolved/Resolved/Fixed)

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 8
8Resolved

The issue was reproduced also on 1.6.0_25, on T1000 and T5440 machines
Java heap size increases after a few days.
Java flags: -DSHVER=1.3,100 -verbose:gc -XX:-ReduceInitialCardMarks -Xms512m -Xmx512m -Dos.heap.max=512m -DREGISTRY_PATH=./registry -DREGISTRY_DEBUG=false

Attached:
jmap1.txt & pmap1.txt were taken on same time - jmap shows 1GB Java heap
jmap2.txt & pmap2.txt show 512m Java heap, but overall process memory is > 2GB.
In both above cases, MaxNewSize==4GB (?!)

Also attached: 'pmap -x' output and 'jinfo -flags' output

> java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) Server VM (build 17.0-b16, mixed mode)

> cat /etc/release
                      Solaris 10 10/09 s10s_u8wos_08a SPARC
           Copyright 2009 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 16 September 2009

EVALUATION Hotspot pre-reserves Java Heap, and commits memory along the way. Total virtual memory may change along the execution, but reserved Java Heap space is not going to change. Close as not reproduciable

24-01-2012