JDK-8025842 : Convert warning("Thread holding lock at safepoint that vm can block on") to fatal(...)
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs25
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-10-02
- Updated: 2015-01-21
- Resolved: 2014-03-04
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.
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 | JDK 9 |
|---|---|
8u40Fixed  |
9 b06Fixed |
Related Reports
|
Relates :
|
Description
Convert warning("Thread holding lock at safepoint that vm can block on") to fatal(...).
Warnings are mostly ignored during testing - tests rarely looks at VM output.
This warning may manifest about serious problem which is hard to diagnose (deadlock between VM thread & suspended Java thread).
The crash log will contain enough information to find the place where a VM lock is taken, since the check is performed on a thread which hold the lock.
Inspired by JDK-8023461.
Comments
|