JDK-4827295 : VM assertion failure in SunOne Appserver7 on solsparc
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 1.4.2
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: generic
  • CPU: generic
  • Submitted: 2003-03-04
  • Updated: 2003-07-08
  • Resolved: 2003-07-08
Related Reports
Relates :  
Description
VM crashed when run the appserver with debug flags:
-server
-XX:CompileThreshold=100
-XX:+ScavengeALot
-XX:ScavengeALotInterval=300
-XX:+WalkStackALot

Appserver is running on solaris sparc 5.8.

Java -version:
java version "1.4.2-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-beta-b17)
Java HotSpot(TM) Server VM (build 20030228200906.jmasa.baseline-fastdebug-debug, mixed mode)

How to reproduce:
 I'll create a reproduciable case in:
   /net/sqesvr.eng/export/vsn/GammaBase/Bugs/{BugID}

Crash Log:
[03/Mar/2003:21:27:23] FINE ( 5509): Status to be set : 0
[03/Mar/2003:21:27:23] FINE ( 5509): Invoked receivedReply()
[03/Mar/2003:21:27:23] FINE ( 5509): J2EE server startup complete.
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # To suppress the following error report, specify this argument
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # after -XX: or in .hotspotrc:  SuppressErrorAt=/buildOopMap.cpp
:208
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: #
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # HotSpot Virtual Machine Error, assertion failure
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # Please report this error at
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # http://java.sun.com/cgi-bin/bugreport.cgi
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: #
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # Java VM: Java HotSpot(TM) Server VM (20030228200906.jmasa.base
line-fastdebug-debug mixed mode)
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: #
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # assert(def, "since live better have reaching def")
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: #
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # Error ID: /net/balvenie.sfbay/export/imgr_home/ws/200302282009
06.jmasa.baseline/src/share/vm/opto/buildOopMap.cpp, 208 [ Patched ]
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: #
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: # Problematic Thread: prio=5 tid=0x00301f68 nid=0x13 runnable
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: #
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: Heap at VM Abort:
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr: Heap
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr:  def new generation   total 3904K, used 225K [0xef800000, 0xefbe
0000, 0xf0d50000)
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr:   eden space 3840K,   5% used [0xef800000, 0xef832610, 0xefbc000
0)
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr:   from space 64K,  37% used [0xefbc0000, 0xefbc5fe0, 0xefbd0000)
[03/Mar/2003:21:27:23] WARNING ( 5509): CORE3283: stderr:   to   space 64K,   0% used [0xefbd0000, 0xefbd0000, 0xefbe0000)
[03/Mar/2003:21:27:29] FINE ( 5508): CORE3061: signal_handler_thread: received signal 18
[03/Mar/2003:21:27:29] FINE ( 5508): CORE3049: Primordial process detected child 5509 died: status 134
[03/Mar/2003:21:27:29] FINE ( 5508): CORE3071: Child died before completing init
[03/Mar/2003:21:27:29] FINE ( 5508): CORE3062: Unlinking of /tmp/server1-4f378e6f/.cgistub_5509 returned -1
[03/Mar/2003:21:27:29] FINE ( 5508): CORE3135: Unlinking /tmp/server1-4f378e6f/iwsadmin.5508

Comments
EVALUATION Please contact madhava about test case he is setting up in Bugs/4827295. ----- Tried multiple times over two days to reproduce bug, and could not get test case to fail running SQE script on SQE machine. ###@###.### 2003-03-18 The machine on which the bug occurs, "impact1" is unreliable and suspect. The bug does not reproduce on the alternative box, "malloc". Am marking as incomplete with the intention of closing the bug. ###@###.### 2003-06-16 This bug is not reproduciable on any other machine other thank impact1..which as Chuck described is very unstable. It could be related to machine problem. If we encounter this problem on a stable machine..will open it again. ###@###.### 2003-07-07
07-07-2003