Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8063301 | 8u45 | Vladimir Ivanov | P4 | Resolved | Fixed | b01 |
JDK-8058357 | 8u40 | Vladimir Ivanov | P4 | Closed | Fixed | b06 |
JDK-8071037 | emb-8u47 | Vladimir Ivanov | P4 | Resolved | Fixed | team |
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 byJDK-8023461.
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
- backported by
-
JDK-8063301 Convert warning("Thread holding lock at safepoint that vm can block on") to fatal(...)
- Resolved
-
JDK-8071037 Convert warning("Thread holding lock at safepoint that vm can block on") to fatal(...)
- Resolved
-
JDK-8058357 Convert warning("Thread holding lock at safepoint that vm can block on") to fatal(...)
- Closed
- relates to
-
JDK-8023461 Thread holding lock at safepoint that vm can block on: MethodCompileQueue_lock
- Closed