JDK-6461897 : nsk/regression/b4324380 fails with java.lang.OutOfMemoryError
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: solaris
  • CPU: x86
  • Submitted: 2006-08-20
  • Updated: 2010-08-05
  • Resolved: 2006-08-25
Related Reports
Relates :  
Description
nsk/regression/b4324380 fails with java.lang.OutOfMemoryError at least on following configurations:

Java Release            : 1.6.0
Java Builds             : b90 - b96
VM flavors              : server
VM Modes                : -Xmixed
Java flags              : -XX:+UseParNewGC -XX:SurvivorRatio=6
Platform(s)             : solaris-amd64
Testbase Name           : SQE Testbase
Suite Name              : nsk.regression
Test cases              : nsk/regression/b4324380

I was not able to reproduce the failure with b89.

Result Dir : 
/net/vmsqe.sfbay/export/weekly/mustang/results/1.6.0-rc-b95/ServerVM/64BITSOL5.11-AMD64/mixed/VM5/nsk.regression-14-WEEKLYmtg-VM5-ServerVM-mixed-64BITSOL5.11-AMD64-2006-08-14-20-59-32/ResultDir/b4324380/

Error Log : 
#==> nsk/regression/b4324380 test LOG:
#--> This test on #4324380 bug; Category: hotspot; Subcategory: runtime_system
#    Synopsis: Thread.join() appears susceptible to race
#
#--> b4324380: test execution time limit = 26 minutes
#--> b4324380: "creator" thread started!
#--> b4324380: test execution time  = 2m. 0s
#-->           number of finished threads for last time interval = 1831060
#-->           total number of finished threads                  = 1831060
#--> b4324380: test execution time  = 4m. 0s
#-->           number of finished threads for last time interval = 1682390
#-->           total number of finished threads                  = 3513450
#--> b4324380: test execution time  = 6m. 0s
#-->           number of finished threads for last time interval = 1265940
#-->           total number of finished threads                  = 4779390
#--> b4324380: test execution time  = 8m. 0s
#-->           number of finished threads for last time interval = 1222790
#-->           total number of finished threads                  = 6002180
#--> b4324380: test execution time  = 10m. 0s
#-->           number of finished threads for last time interval = 1165910
#-->           total number of finished threads                  = 7168090
#--> b4324380: test execution time  = 12m. 0s
#-->           number of finished threads for last time interval = 1303180
#-->           total number of finished threads                  = 8471270
#--> b4324380: test execution time  = 14m. 0s
#-->           number of finished threads for last time interval = 1167900
#-->           total number of finished threads                  = 9639170
##
## An unexpected error has been detected by Java Runtime Environment:
##
## java.lang.OutOfMemoryError: requested 1752 bytes for CHeapObj-new. Out of swap space?
##
##  Internal Error (414C4C4F434154494F4E0E494E4C494E450E4850500017), pid=9447, tid=13
##
## Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0-rc-b95 mixed mode)
## An error report file with more information is saved as hs_err_pid9447.log
##
## If you would like to submit a bug report, please visit:
##   http://java.sun.com/webapps/bugreport/crash.jsp
##

How to reproduce :
 1. ssh vm-v20z-9.sfbay
 2. cd /net/vmsqe.sfbay/export/weekly/mustang/results/1.6.0-rc-b95/ServerVM/64BITSOL5.11-AMD64/mixed/VM5/nsk.regression-14-WEEKLYmtg-VM5-ServerVM-mixed-64BITSOL5.11-AMD64-2006-08-14-20-59-32/ResultDir/b4324380/
 3. sh b4324380.tlog_bXX b96

Comments
WORK AROUND Fixed by applying Solaris 10 patch 119964-07
25-08-2006

EVALUATION Caused by a problem in the Solaris C++ runtime on AMD64 systems - see CR 6391358. Fixed by applying patch 119964-07
25-08-2006