JDK-6380402 : JVM crash when runing the Collector with Java profiling on for xalan benchmark
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_suse_sles_9
  • CPU: x86
  • Submitted: 2006-02-02
  • Updated: 2010-05-10
  • Resolved: 2008-05-19
Related Reports
Duplicate :  
Relates :  
Description
J2SE Version (please include all output from java -version flag):
  Java HotSpot(TM) Server VM (build 1.6.0-rc-b67 mixed mode) )

Does this problem occur on J2SE 1.4.x or 5.0.x ?  Yes / No (pick one) 
  No

Operating System Configuration Information (be specific): 
   SLES9 (64bit) (2.6.5-7.97)

Hardware Configuration Information (be specific):
   V40Z system, Opteron 875 - 4#, 16Gs of memory.

Bug Description: 

   Bug for: java/hotspot/runtime_system

   Got the following error when running the Collector with Java profiling 
   on for xalan benchmark which is included in the DaCapo suite.

#
# An unexpected error has been detected by Java Runtime Environment:
#
#  Internal Error (53484152454432554E54494D450E435050024C), pid=7204, tid=1077061984
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0-rc-b67 mixed mode)
# An error report file with more information is saved as hs_err_pid7204.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

Aborted

Steps to Reproduce (be specific):
   Download the suite from  - http://www-ali.cs.umass.edu/DaCapo/gcbm/dacapo-beta051009.jar

   Run Collector, for Performance Analyzer that is packaged with Sun Studio 11, with the 
   1.6.0-rc-b67 JVM for 64 bit with Java profiling on.

   Commandline: collector -j on /64bitjdk-path/bin/java Harness -s large xalan

Comments
EVALUATION Since this is likely a problem with AsyncGetCalltrace(), I'm lowering the priority from P3 to P4. AsyncGetCalltrace() bugs are dealt with near the end of a release cycle when other changes are less likely to perturb the careful dance that must be done to get a calltrace asynchronously.
08-03-2006