JDK-6977180 : fatal error: acquiring lock Heap_lock/17 out of order with lock Threads_lock/15, mutex.cpp:1293
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2010-08-13
  • Updated: 2013-05-16
  • Resolved: 2013-05-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Related Reports
Duplicate :  
Description
The nightly test:

sun/management/HotspotThreadMBean/GetInternalThreads.java

failed with the following error:

----------System.out:(21/1074)----------
Internal Thread Count = 35
 Locks owned:
Mutex: [0x108c718/0x1] Threads_lock - owner: 0x7f39e42c2800
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=/mutex.cpp:1293
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/tmp/jprt/P1/B/202649.jcoomes/source/src/share/vm/runtime/mutex.cpp:1293), pid=8306, tid=139882067315024
#  fatal error: acquiring lock Heap_lock/17 out of order with lock Threads_lock/15 -- possible deadlock
#
# JRE version: 7.0
# Java VM: OpenJDK 64-Bit Server VM (19.0-b04-201008112026.jcoomes.6976378-taskqueue-p-fastdebug mixed mode linux-amd64 )
# An error report file with more information is saved as:
# /export/local/37383.JDK7.NIGHTLY.VM+linux-amd64_javase_server_mixed_JT_JDK_sun_management/results/workDir/sun/management/HotspotThreadMBean/GetInternalThreads/hs_err_pid8306.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Current thread is 139882067315024
Dumping core ...

The stack trace is:

Stack: [0x00007f38d4dec000,0x00007f38d4eed000],  sp=0x00007f38d4eeaae0,  free space=3fa0000000000000018k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.so+0xa7e0fc];;  _ZN7VMError6reportEP12outputStream+0x116c
V  [libjvm.so+0xa7e4ca];;  _ZN7VMError14report_and_dieEv+0x2da
V  [libjvm.so+0x4ab094];;  _Z15report_vm_errorPKciS0_S0_+0x84
V  [libjvm.so+0x853816];;  _ZN7Monitor24set_owner_implementationEP6Thread+0x1a6
V  [libjvm.so+0x853d37];;  _ZN7Monitor4lockEP6Thread+0x97
V  [libjvm.so+0x54e0b7];;  _ZN15G1CollectedHeap12mem_allocateEmbbPb+0x57
V  [libjvm.so+0x54e3e8];;  _ZN15G1CollectedHeap17allocate_new_tlabEm+0x18
V  [libjvm.so+0x40d36f];;  _ZN13CollectedHeap23allocate_from_tlab_slowEP6Threadm+0x1ef
V  [libjvm.so+0x2ef1a9];;  _ZN13CollectedHeap24common_mem_allocate_initEmbP6Thread+0xc9
V  [libjvm.so+0xa42fc9];;  _ZN14typeArrayKlass8allocateEiP6Thread+0x2c9
V  [libjvm.so+0x625426];;  _ZN16java_lang_String12basic_createEibP6Thread+0xb6
V  [libjvm.so+0x62a6e7];;  _ZN16java_lang_String15create_from_strEPKcP6Thread+0x37
V  [libjvm.so+0x7e47e4];;  _ZN18ThreadTimesClosure9do_threadEP6Thread+0xb4
V  [libjvm.so+0xaa58bf];;  _ZNK16AbstractWorkGang10threads_doEP13ThreadClosure+0x4f
V  [libjvm.so+0x541966];;  _ZNK15G1CollectedHeap13gc_threads_doEP13ThreadClosure+0x26
V  [libjvm.so+0xa1c223];;  _ZN7Threads10threads_doEP13ThreadClosure+0x73
V  [libjvm.so+0x7e3032];;  jmm_GetInternalThreadTimes+0x362
j  sun.management.HotspotThread.getInternalThreadTimes0([Ljava/lang/String;[J)I+0
j  sun.management.HotspotThread.getInternalThreadCpuTimes()Ljava/util/Map;+25
j  GetInternalThreads.main([Ljava/lang/String;)V+140
v  ~StubRoutines::call_stub

The link to the test directory is:

http://sqeweb.sfbay/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2010-08-12/G1_GC_Baseline/javase/linux-amd64/server/mixed/linux-amd64_javase_server_mixed_JT_JDK_sun_management/workDir/sun/management/HotspotThreadMBean/

Comments
This seems to have been fixed by JDK-7196045 / http://hg.openjdk.java.net/hsx/hotspot-main/hotspot/rev/6af8f3562069
13-05-2013