JDK-6735499 : crash in 1.6.0_04 in libjvm.so:revoke_bias()
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs10,hs11,6u6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic,solaris_10
  • CPU: generic,sparc
  • Submitted: 2008-08-08
  • Updated: 2011-02-16
  • Resolved: 2009-01-19
Related Reports
Duplicate :  
Relates :  
Hardware: Sun T2000
Memory: 16 GB
OS: Solaris 10

java version "1.6.0_04"
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Server VM (build 10.0-b19, mixed mode)

Sun Java System Application Server 9.1_01 (build b09d-fcs)

All files under /net/cores.central/cores/66037713/66037713-08-07-08/pkgcore1

(dbx) thread t@18
t@18 (l@18) stopped in __lwp_kill at 0xff2c5bf0
0xff2c5bf0: __lwp_kill+0x0008:  bcc,a,pt  %icc,__lwp_kill+0x18  ! 0xff2c5c00
(dbx) where -l
current thread: t@18
=>[1] libc.so.1:__lwp_kill(0x0, 0x6, 0xfef66c10, 0xad314, 0xff2f12d8, 0x0), at 0xff2c5bf0
  [2] libc.so.1:raise(0x6, 0x0, 0xff2f2ed0, 0xfee6d5bc, 0xffffffff, 0x6), at 0xff264bf4
  [3] libc.so.1:abort(0x0, 0x1, 0xfef66c10, 0xad314, 0xff2f12d8, 0x0), at 0xff2410f8
  [4] libjvm.so:os::abort(0x1, 0xff1014f4, 0x1, 0xff0ea000, 0x174f4, 0x17400), at 0xfee6d5bc
  [5] libjvm.so:VMError::report_and_die(0xff121ff0, 0x0, 0x1, 0xff0b25ff, 0xfef73bb2, 0x17400), at 0xfef66c10
  [6] libjvm.so:JVM_handle_solaris_signal(0xb, 0x701ff838, 0x701ff580, 0x8b000, 0x644800, 0xfeadede4), at 0xfe9a5dc8
  [7] libc.so.1:__sighndlr(0xb, 0x701ff838, 0x701ff580, 0xfe9a532c, 0x0, 0x1), at 0xff2c4b28
  ---- called from signal handler with signal 11 (SIGSEGV) ------
  [8] libjvm.so:revoke_bias(0x7cca7be0, 0x0, 0x90009, 0x0, 0x178f485, 0x0), at 0xfeadede4
  [9] libjvm.so:VM_RevokeBias::doit(0x60ffbd48, 0xa4, 0x644b70, 0xff101d24, 0x644800, 0x724f10), at 0xfeae0c58
  [10] libjvm.so:VM_Operation::evaluate(0x60ffbd48, 0x2dcb0, 0xff0ea000, 0xfe5, 0x7f2b41, 0x36c00), at 0xfe9c516c
  [11] libjvm.so:VMThread::evaluate_operation(0x2dcb0, 0x60ffbd48, 0x644b70, 0x7f2b41, 0x644b78, 0xff0ea000), at 0xfef69de4
  [12] libjvm.so:VMThread::loop(0x0, 0xfead7050, 0x2c944, 0x0, 0x44800, 0x5ca468), at 0xfef6a37c
  [13] libjvm.so:VMThread::run(0x644800, 0x36000, 0xff120350, 0xff0ea000, 0x36350, 0x36000), at 0xfea4fa08
  [14] libjvm.so:java_start(0x644800, 0x10, 0x12c9, 0xff0ea000, 0xff05cfa5, 0xff121904), at 0xfee6c940

Java Flags:

argv[52]: -server
argv[53]: -XX:+UnlockDiagnosticVMOptions
argv[54]: -XX:+UseConcMarkSweepGC
argv[55]: -XX:+UseParNewGC
argv[56]: -XX:MaxNewSize=1280M
argv[57]: -XX:NewSize=1280M
argv[58]: -Xms2024m
argv[59]: -XX:+PrintGCDetails
argv[60]: -verbosegc
argv[61]: -XX:+PrintGCTimeStamps
argv[62]: -javaagent:/var/opt/wily/Agent.jar
argv[63]: -XX:MaxPermSize=192m
argv[64]: -Xmx2024m
argv[65]: -XX:+LogVMOutput
argv[66]: -XX:LogFile=/opt/SUNWappserver/nodeagents/sasbas21-node/sasbas21-int/logs/jvm.log
argv[67]: -cp
argv[68]: /opt/SUNWappserver/lib/jhall.jar:/opt/SUNWappserver/lib/appserv-launch.jar

EVALUATION This appears to be the same bug as 6676175.