JDK-6257178 : HotSpot crashed in ~RuntimeStub::_complete_monitor_locking_Java
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_redhat_3.0
  • CPU: sparc
  • Submitted: 2005-04-19
  • Updated: 2010-08-03
  • Resolved: 2005-06-23
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
While I was working on 6210996 (ResourceBundle problem), HotSpot crashed. The log file and test program are in Attachments.

The following is the output to the terminal where the test program was running. It ran for more than 9 hours. I was also running jconsole to monitor JVM.

# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0xb6eeab05, pid=19355, tid=2928094128
#
# Java VM: Java HotSpot(TM) Server VM (1.6.0-ea-b31 mixed mode)
# Problematic frame:
# V  [libjvm.so+0x3e6b05]
#
# An error report file with more information is saved as hs_err_pid19355.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Command terminated by signal 6
2.33user 2.11system 9:04:40elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1446major+7779minor)pagefaults 0swaps

###@###.### 2005-04-19 03:13:07 GMT

Comments
EVALUATION This appears to be identical to 6288902 which is caused by passing a bad thread value to the locking code if called from a sync native method. The test for 6288902 would crash with the same call stack as this bug. ###@###.### 2005-06-23 14:11:43 GMT
19-04-2005