. xxxxx@xxxxx  2003-02-19

Stress testing of the AsyncGetCallTrace() interface has exposed an
intermittent assertion failure:

# assert(pc_desc != 0, "scopeDesc must exist")
# Error ID: src/share/vm/runtime/vframe.cpp, 524

During the stack walk, vframeStream finds a compiled frame for which it
cannot find a scope description. Here is a snippet of the stack trace:

  [6] report_assertion_failure(code_str = 0xfefdebdb "pc_desc != 0", file_name =
 0xfefdebe8 "/work/ws/hotspot/main/baseline-exp/src/share/vm/runtime/vframe.cpp"
, line_no = 524, message = 0xfefdec2b "scopeDesc must exist"), line 237 in "debu
g.cpp"
  [7] vframeStream::fill_from_frame(this = 0xffbed538), line 524 in "vframe.cpp"
  [8] vframeStream::vframeStream(this = 0xffbed538, thread = 0x3e440, top_frame
= CLASS, stop_at_java_call_stub = 0), line 572 in "vframe.cpp"
  [9] forte_fill_call_trace_given_top(thd = 0x3e440, trace = 0xfc6a1850, depth =
 50, top_frame = CLASS), line 177 in "forte.cpp"
  [10] AsyncGetCallTrace(trace = 0xfc6a1850, depth = 50, ucontext = 0xffbed9b8),
 line 313 in "forte.cpp"
  [11] profhandler(0x1d, 0xffbedc70, 0xffbed9b8, 0x0, 0x0, 0x0), at 0xfc690c3c
  [12] __sighndlr(0x1d, 0xffbedc70, 0xffbed9b8, 0xfc690a80, 0x0, 0x0), at 0xff37
4c8c
  [13] call_user_handler(0xff3875a8, 0x1, 0xff387b20, 0xffbed9b8, 0xffbedc70, 0x
1d), at 0xff36fadc
  [14] sigacthandler(0xff3875a8, 0xffbedc70, 0xffbed9b8, 0xff386000, 0xffbedc70,
 0x1d), at 0xff36fca8
  ---- called from signal handler with signal -13077080 (SIG-13077080) ------
  [15] 0xf9d02c04(0xf18283c0, 0xf18283a8, 0x8, 0x0, 0xffbee120, 0x3ea58), at 0xf
9d02c03
  [16] 0xf9c001c8(0xffbedde0, 0xffbee038, 0xa, 0xf5844d18, 0xf9c0c560, 0xffbee10
4), at 0xf9c001c7
  [17] JavaCalls::call_helper(result = 0xffbee030, m = 0xffbedf8c, args = 0xffbe
e0f8, __the_thread__ = 0x3e440), line 364 in "javaCalls.cpp"

The full stack trace for the java_g crash is attached as threads.log.4.

This failure reproduces in a different way with the java cmd:

# Error ID: 43113F32554E54494D45110E4350500308 01

The ErrorID maps to: c1_Runtime1.cpp, 776

The code is in src/share/vm/c1/c1_Runtime1.cpp:
Runtime1::return_address_for_exception():

  // exception must have happened inside an nmethod
  CodeBlob* cb = CodeCache::find_blob(pc);
  guarantee(cb != NULL && cb->is_nmethod(),
    "exception happened outside interpreter, nmethods and vtable stubs");

Here is a snippet of the stack trace:

  [6] report_fatal(0xfefa73bc, 0x308, 0xfefa73ff, 0x0, 0x0, 0x0), at 0xfee355f4
  [7] Runtime1::return_address_for_exception(0x0, 0xfa46f800, 0x0, 0x0, 0x0, 0x0
), at 0xfeded558
  [8] 0xfa46f804(0x0, 0xfa4871c4, 0x1, 0xfa4871c4, 0x31ef98, 0xfecd2da8), at 0xf
a46f803
  [9] vframeStream::fill_from_frame(0xffbed858, 0x0, 0xffbed870, 0x0, 0x20, 0x0)
, at 0xfecd2e74
  [10] vframeStream::vframeStream(0xffbed858, 0x2ccd0, 0xffbed848, 0x0, 0xffbed9
b8, 0x0), at 0xfef851b4
  [11] forte_fill_call_trace_given_top(0x2ccd0, 0xfcfc1850, 0x32, 0xffbeda30, 0x
0, 0x0), at 0xfee3b244
  [12] AsyncGetCallTrace(0xfcfc1850, 0x32, 0xffbedcb0, 0x0, 0x0, 0xfcfc17c0), at
 0xfee3b628
  [13] profhandler(0x1d, 0xffbedf68, 0xffbedcb0, 0x0, 0x0, 0x0), at 0xfcfb0c3c
  [14] __sighndlr(0x1d, 0xffbedf68, 0xffbedcb0, 0xfcfb0a80, 0x0, 0x0), at 0xff37
4c8c
  [15] call_user_handler(0xff3875a8, 0x1, 0xff387b20, 0xffbedcb0, 0xffbedf68, 0x
1d), at 0xff36fadc
  [16] sigacthandler(0xff3875a8, 0xffbedf68, 0xffbedcb0, 0xff386000, 0xffbedf68,
 0x1d), at 0xff36fca8
  ---- called from signal handler with signal -13077080 (SIG-13077080) ------
  [17] 0xfa486fc4(0xf2075a78, 0xf2075a60, 0x0, 0xf6001e00, 0x337940, 0xfecba1e4)
, at 0xfa486fc3
  [18] 0xfa400118(0xffbee0d8, 0xffbee240, 0xa, 0xf6042c30, 0xfa40aae0, 0xffbee2f
4), at 0xfa400117
  [19] JavaCalls::call_helper(0xffbee238, 0xffbee190, 0xffbee2ec, 0x2ccd0, 0x2cc
d0, 0x0), at 0xfecc7534

The full stack trace for the java crash is attached as threads.log.2.

N/A

 xxxxx@xxxxx  2003-02-19

Steve G. and I have exchanged a number of e-mail messages about this bug.

What we discovered is that the SIGPROF signal has come in right in the
middle of a Java call. There is a compiled frame on the stack that is
starting to make a call to another Java method. When we ask for the
current frame what we get back is a combination of information from
two frames:

- some information is from the compiled frame (the real sender)
- some information is from the new frame (the callee)

We try to use this mix of information to find the "sender" of the
current frame. However, this doesn't work quite right because the
current frame is not completely setup. We wander up the call stack
until we fail an assertion with java_g or crash with java.

The vframeStream code is working correctly for the regular system
and we don't want to change that. The problem that we are seeing with
AsyncGetCallTrace() is limited to that API only. In the regular
system, the new frame (the callee) is stable by the time any
stack walker tries to do its work. It is the asynchronous nature of
AsyncGetCallTrace() that is allowing the API to see the incomplete
stack frame.

I just got this error id 
(43113F32554E54494D45110E4350500308) and I'm 
using Java HotSpot(TM) Client VM (1.4.2_03-b02 
mixed mode), so evidently the bug is not fixed.

We got this error id when running code that made extensive
uses of arrays and files. The code was compiled on the 1.2
JVM. The error message appears if you try and run it against
the 1.3 or 1.4 JVM's on Windows. The error does not occur if
you compile under 1.4.  In addition to the "HotSpot Virtual
Machine Error, Internal Error" message the application might
simply vanish or produce the Microsoft "Send us your bug"
window.

I have the same error-id
I am working under  linux 2.4.18-14, and after 2 or 3 
hours, the JVM abort without sending any throwable 
exception.
The only message received is:
# 
# HotSpot Virtual Machine Error, Internal Error 
# Please report this error at 
# http://java.sun.com/cgi-bin/bugreport.cgi 
# 
# Java VM: Java HotSpot(TM) Client VM (1.4.2_04-b05 
mixed mode) 
# 
# Error ID: 
43113F32554E54494D45110E4350500308 
# 
# Problematic Thread: prio=1 tid=0x08458978 
nid=0x6b63 runnable 
# 
Heap at VM Abort: 
Heap 
def new generation total 7168K, used 6398K 
[0x44680000, 0x44e40000, 0x45a3000 
0) 
eden space 6400K, 99% used [0x44680000, 
0x44cbfbf8, 0x44cc0000) 
from space 768K, 0% used [0x44cc0000, 0x44cc0000, 
0x44d80000) 
to space 768K, 0% used [0x44d80000, 0x44d80000, 
0x44e40000) 
tenured generation total 94528K, used 22458K 
[0x45a30000, 0x4b680000, 0x54680 
000) 
the space 94528K, 23% used [0x45a30000, 
0x4701ea78, 0x4701ec00, 0x4b680000) 
compacting perm gen total 6912K, used 6809K 
[0x54680000, 0x54d40000, 0x5868000 
0) 
the space 6912K, 98% used [0x54680000, 
0x54d26450, 0x54d26600, 0x54d40000) 

I just saw the same error number in 1.4.2_04 on linux. Obviously not fixed.

$ uname -a
Linux titanium 2.4.10-4GB #1 Fri Sep 28 17:20:21 GMT 2001 i686 
unknown

$ java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_04-b05 mixed mode)
#
# Error ID: 43113F32554E54494D45110E4350500308
#
# Problematic Thread: prio=1 tid=0x08053c78 nid=0x7f3b runnable
#

Heap at VM Abort:
Heap
 def new generation   total 576K, used 159K [0x44700000, 0x447a0000, 
0x44be0000)
  eden space 512K,  25% used [0x44700000, 0x44720588, 0x44780000)
  from space 64K,  47% used [0x44790000, 0x44797958, 0x447a0000)
  to   space 64K,   0% used [0x44780000, 0x44780000, 0x44790000)
 tenured generation   total 1408K, used 321K [0x44be0000, 0x44d40000, 
0x48700000)
   the space 1408K,  22% used [0x44be0000, 0x44c30458, 0x44c30600, 
0x44d40000)
 compacting perm gen  total 4096K, used 2339K [0x48700000, 
0x48b00000, 0x4c700000)
   the space 4096K,  57% used [0x48700000, 0x48948e38, 0x48949000, 
0x48b00000)

In case it's useful, I was running ant at the time.

  to   space 64K,   0% used [0x447c0000, 0x447c0000, 0x447d0000)
 tenured generation   total 2012K, used 1802K [0x45110000,
0x45307000, 0x4c740000)
   the space 2012K,  89% used [0x45110000, 0x452d28c0,
0x452d2a00, 0x45307000)
 compacting perm gen  total 5376K, used 5240K [0x4c740000,
0x4cc80000, 0x50740000)
   the space 5376K,  97% used [0x4c740000, 0x4cc5e140,
0x4cc5e200, 0x4cc80000)


------
  When I tried on 1.5.0-beta, this bug error did not occur.

$ java -version
java version "1.5.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0-beta-b32c)
Java HotSpot(TM) Client VM (build 1.5.0-beta-b32c, mixed mode)

I got same Error Id on Linux. I think that this bug is not
fixed.

 Linux is the following versions.
 2.4.9-e.24 #1 Tue May 27 16:15:51 EDT 2003 i686 unknown

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_04-b05 mixed mode)
#
# Error ID: 43113F32554E54494D45110E4350500308
#
# Problematic Thread: prio=1 tid=0x08052ce0 nid=0x25e2 runnable
#

Heap at VM Abort:
Heap
 def new generation   total 576K, used 466K [0x44740000,
0x447e0000, 0x45110000)
  eden space 512K,  78% used [0x44740000, 0x447a48d0,
0x447c0000)
  from space 64K, 100% used [0x447d0000, 0x447e0000, 0x447e0000)
  to   space 64K,   0% used [0x447c0000, 0x447c0000, 0x447d0000)
 tenured generation   total 2012K, used 1802K [0x45110000,
0x45307000, 0x4c740000)
   the space 2012K,  89% used [0x45110000, 0x452d28c0,
0x452d2a00, 0x45307000)
 compacting perm gen  total 5376K, used 5240K [0x4c740000,
0x4cc80000, 0x50740000)
   the space 5376K,  97% used [0x4c740000, 0x4cc5e140,
0x4cc5e200, 0x4cc80000)


------
  When I tried on 1.5.0-beta, this bug error did not occur.

$ java -version
java version "1.5.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0-beta-b32c)
Java HotSpot(TM) Client VM (build 1.5.0-beta-b32c, mixed mode)

Not fixed! We get:
May 10 16:11:04 2004: #
May 10 16:11:04 2004: # HotSpot Virtual Machine Error, 
Internal Error
May 10 16:11:04 2004: # Please report this error at
May 10 16:11:04 2004: # http://java.sun.com/cgi-
bin/bugreport.cgi
May 10 16:11:04 2004: #
May 10 16:11:04 2004: # Java VM: Java HotSpot(TM) 
Client VM (1.4.2_04-b05 mixed 
mode)
May 10 16:11:04 2004: #
May 10 16:11:04 2004: # Error ID: 
43113F32554E54494D45110E4350500308
May 10 16:11:04 2004: #
May 10 16:11:04 2004: # Problematic Thread: 
May 10 16:11:04 2004: prio=5 tid=0x43b9b920 
May 10 16:11:04 2004: nid=0x684 
May 10 16:11:04 2004: runnable 
May 10 16:11:04 2004: 
May 10 16:11:04 2004: #
May 10 16:11:04 2004: 
May 10 16:11:04 2004: Heap at VM Abort:
May 10 16:11:04 2004: 
May 10 16:11:04 2004: Heap
May 10 16:11:04 2004:  def new generation  
May 10 16:11:04 2004:  total 4224K, used 2010K
May 10 16:11:04 2004:  [0x1f800000, 0x1fc90000, 
0x21e70000)
May 10 16:11:04 2004:   eden
May 10 16:11:04 2004:  space 3776K,  45% used
May 10 16:11:04 2004:  [0x1f800000, 0x1f9acfd0, 
0x1fbb0000)
May 10 16:11:04 2004:   from
May 10 16:11:04 2004:  space 448K,  65% used
May 10 16:11:04 2004:  [0x1fbb0000, 0x1fbf9b58, 
0x1fc20000)
May 10 16:11:04 2004:   to  
May 10 16:11:04 2004:  space 448K,   0% used
May 10 16:11:04 2004:  [0x1fc20000, 0x1fc20000, 
0x1fc90000)
May 10 16:11:04 2004:  tenured generation  
May 10 16:11:04 2004:  total 55484K, used 29340K
May 10 16:11:04 2004:  [0x21e70000, 0x2549f000, 
0x3ec00000)
May 10 16:11:04 2004:    the
May 10 16:11:04 2004:  space 55484K,  52% used
May 10 16:11:04 2004:  [0x21e70000, 0x23b170d0, 
0x23b17200, 0x2549f000)
May 10 16:11:04 2004:  compacting perm gen 
May 10 16:11:04 2004:  total 21504K, used 21380K
May 10 16:11:04 2004:  [0x3ec00000, 0x40100000, 
0x42c00000)
May 10 16:11:04 2004:    the
May 10 16:11:04 2004:  space 21504K,  99% used
May 10 16:11:04 2004:  [0x3ec00000, 0x400e1220, 
0x400e1400, 0x40100000)
May 10 16:11:04 2004: Java VM aborting...

Got this as well:

uname -a
Linux shrek 2.4.21-4.ELhugemem #1 SMP Fri Oct 3 17:31:20 EDT 2003 i686 i686 i386 GNU/Linux

#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_04-b05 mixed mode)

#

# Error ID: 43113F32554E54494D45110E4350500308

#

# Problematic Thread: prio=1 tid=0x068deb88 nid=0x199e runnable

#

 

Heap at VM Abort:

Heap

 def new generation   total 146304K, used 20K [0x0cec0000, 0x16d70000, 0x1e3a0000)

  eden space 130112K,   0% used [0x0cec0000, 0x0cec6188, 0x14dd0000)

  from space 16192K,   0% used [0x14dd0000, 0x14dd0000, 0x15da0000)

  to   space 16192K,   0% used [0x15da0000, 0x15da0000, 0x16d70000)

 tenured generation   total 1948872K, used 2560318K [0x1e3a0000, 0x952d2000, 0xedec0000)

   the space 1948872K, 131% used [0x1e3a0000, 0xba7ef9b0, 0xba7efa00, 0x952d2000)

 compacting perm gen  total 32768K, used 32706K [0xedec0000, 0xefec0000, 0xf1ec0000)

   the space 32768K,  99% used [0xedec0000, 0xefeb0aa8, 0xefeb0c00, 0xefec0000)

I can consistently reproduce this on linux 1.4.2_06 (running our app in weblogic).


uname -a
Linux topdog 2.4.19-64GB-SMP #1 SMP Mon Oct 21 18:48:05 UTC 2002 i686 unknown
java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)


#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode)
#
# Error ID: 43113F32554E54494D45110E4350500308
#
# Problematic Thread: prio=1 tid=0x08201d78 nid=0x1189 runnable
#

We are seeing the same error on Windows XP SP2 w/ JDK1.4.2_08-b3 mixed mode
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_08-b03 mixed mode)
#
# Error ID: 43113F32554E54494D45110E4350500308
#
# Problematic Thread: prio=7 tid=0x008d3ea0 nid=0xb24 runnable 
#

Heap at VM Abort:
Heap
 def new generation   total 576K, used 41K [0x10010000, 0x100b0000, 0x104f0000)
  eden space 512K,   6% used [0x10010000, 0x10017df0, 0x10090000)
  from space 64K,  16% used [0x10090000, 0x10092908, 0x100a0000)
  to   space 64K,   0% used [0x100a0000, 0x100a0000, 0x100b0000)
 tenured generation   total 6764K, used 5211K [0x104f0000, 0x10b8b000, 0x14010000)
   the space 6764K,  77% used [0x104f0000, 0x10a06d80, 0x10a06e00, 0x10b8b000)
 compacting perm gen  total 11264K, used 11158K [0x14010000, 0x14b10000, 0x18010000)
   the space 11264K,  99% used [0x14010000, 0x14af5928, 0x14af5a00, 0x14b10000)

I encountered the same problem. After a little soul (and project) searching it turned out that I had a ClassLoader problem which triggered this error. I had a classes12.jar (Oracle driver for jdk1.2) in my container classloader and a ojdbc14.jar (Oracle driver for jdk1.4) in my webapp classloader. After removing the classes12.jar and putting the ojdbc14 in the container classpath my problem was fixed

I have same error id
 
# HotSpot Virtual Machine Error, Internal Error 
# Please report this error at 
# http://java.sun.com/cgi-bin/bugreport.cgi 
# 
# Java VM: Java HotSpot(TM) Client VM (1.4.2_07-b05 
mixed mode) 
# 
# Error ID: 
43113F32554E54494D45110E4350500308 
# 
# Problematic Thread: prio=1 tid=0x739ed930 
nid=0x868 runnable 
# 
Heap at VM Abort: 
Heap 
def new generation total 36352K, used 11875K 
[0x10010000, 0x12780000, 0x1737000) 
eden space 32320K, 34% used [0x10010000, 
0x10afcd28, 0x11fa0000) 
from space 4032K, 17% used [0x12390000, 0x1243bed8, 0x12780000) 
to space 4032K, 0% used [0x11fa0000, 0x11fa0000, 
0x12390000) 
tenured generation total 483968K, used 173097K 
[0x17370000, 0x34c10000, 0x6dc10000) 
the space 483968K, 35% used [0x17370000, 
0x21c7a780, 0x21c7a800, 0x34c10000) 
compacting perm gen total 46848K, used 46691K 
[0x6dc10000, 0x709d0000, 0x71c10000) 
the space 46848K, 99% used [0x6dc10000, 
0x709a8fb0, 0x709a9000, 0x709d0000) 

The bug is happening for me as well in a later JVM version: 
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  Internal Error (43113F32554E54494D45110E4350500308), pid=3160, tid=5512
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_09-b05 mixed mode)
# An error report file with more information is saved as hs_err_pid3160.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Dynamo exited abnormally.  For troubleshooting information go to the URL:
  http://www.atg.com/support