JDK-6209695 : VolanoTest OOM with mustang b14
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 6
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris,solaris_8,solaris_9
  • CPU: sparc
  • Submitted: 2004-12-16
  • Updated: 2010-04-02
  • Resolved: 2005-02-01
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 Availabitlity Release.

To download the current JDK release, click here.
Other JDK 6
1.3.1_17Fixed 6 b22Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
VTest client OOM with Mustang b14 on jtg-e220-3

JVM flags used: -client  -XX:+UseSerialGC
java version:
Java HotSpot(TM) Client VM (build 1.6.0-ea-b14, mixed mode, sharing)

# uname -a
SunOS jtg-e220-3 5.8 Generic_108528-29 sun4u sparc SUNW,Ultra-60
# psrinfo
0       on-line   since 09/21/04 18:16:39
2       on-line   since 09/21/04 18:16:40

VolanoTest client process OOM. The frequency is about 0.2%. The OOM
is reproducible with mustang b14, but not with mustang b13.


###@###.### 2004-12-16 20:11:06 GMT


_____________________________________________________________________

This problem has appeared again on the Mustang B19 on jtg-e220-1
JVM flags used: -client  -XX:+UseSerialGC
Problem apperaed after : 5 days,22 hours 56 minutes
System Used : jtg-e220-1
java version: build 1.6.0-ea-b19

Error message

Jan 19 11:26 VolanoTestrun.1903.-client/run.vtest.out

VolanoTest failed after 5 days: 22 hours 56 minutes 
server pid: 2114

Java HotSpot(TM) Client VM (build 1.6.0-ea-b19, mixed mode, sharing)
Unexpected error for Test6 in Room2 (java.lang.OutOfMemoryError: Java heap space).
Unexpected error for Test19 in Room1 (java.lang.OutOfMemoryError: Java heap space).
Unexpected error for Test18 in Room1 (java.lang.OutOfMemoryError: Java heap space).
Unexpected error for Test10 in Room2 (java.lang.OutOfMemoryError: Java heap space).
Unexpected error for Test4 in Room2 (java.lang.OutOfMemoryError: Java heap space).
Unexpected error for Test9 in Room2 (java.lang.OutOfMemoryError: Java heap space).[GC [DefNew: 2089K->64K(2112K), 0.0557926 secs][Tenured: 2460K->1452K(2560K), 0.0974101 secs] 3497K->1452K(4672K), 0.1539849 secs]
Exception in thread "Sender-175" java.lang.OutOfMemoryError: Java heap space
Unexpected error for Test7 in Room2 (java.lang.OutOfMemoryError: Java heap space).
Unexpected error for Test11 in Room2 (java.lang.OutOfMemoryError: Java heap space).



###@###.### 2005-1-22 01:17:48 GMT

Comments
SUGGESTED FIX See http://analemma.sfbay.sun.com/net/spot/scratch/ysr/bugs/webrev/ ###@###.### 2005-1-05 00:33:44 GMT
2005-01-05

WORK AROUND Set -Xmx and -Xms to the same value to avoid this problem (but you might still run into the day one bug documented in 6186200, which will be fixed later in Mustang). ###@###.### 2004-12-20 22:39:22 GMT
2004-12-20

EVALUATION The code in 5101236 to avoid STW GC attempts when GC is locked out, should have instead expanded the heap when possible. ###@###.### 2004-12-20 22:39:22 GMT
2004-12-20