United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7196045 Possible JVM deadlock in ThreadTimesClosure when using HotspotInternal non-public API.
JDK-7196045 : Possible JVM deadlock in ThreadTimesClosure when using HotspotInternal non-public API.

Details
Type:
Bug
Submit Date:
2012-09-04
Status:
Closed
Updated Date:
2014-01-14
Project Name:
JDK
Resolved Date:
2012-09-20
Component:
hotspot
OS:
generic
Sub-Component:
svc
CPU:
generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
6u33
Fixed Versions:
hs25 (b03)

Related Reports
Backport:
Backport:
Backport:
Backport:
Backport:
Backport:
Duplicate:

Sub Tasks

Description
SHORT SUMMARY: hang in sun.management.HotspotInternal
INDICATORS: JVM lockup, ThreadTimesClosure::do_thread creating String
COUNTER INDICATORS:
TRIGGERS: calling sun.management.HotspotInternal, and hitting a GC
KNOWN WORKAROUND: none
PRESENT SINCE:
HOW TO VERIFY:
NOTES FOR SE: ThreadTimesClosure::do_thread called with Threads_lock, must 
avoid allocating Java objects.
REGRESSION:

                                    

Comments
EVALUATION

String allocation while holding the Threads_lock means we deadlock if a GC happens at that point.
                                     
2012-09-04
URL:   http://hg.openjdk.java.net/hsx/hotspot-main/hotspot/rev/6af8f3562069
User:  dsamersoff
Date:  2012-09-27 18:41:59 +0000

                                     
2012-09-27
URL:   http://hg.openjdk.java.net/hsx/hsx25/hotspot/rev/6af8f3562069
User:  amurillo
Date:  2012-09-28 22:30:08 +0000

                                     
2012-09-28
EVALUATION

http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/6af8f3562069
                                     
2012-09-20



Hardware and Software, Engineered to Work Together