JDK-8144702 : Using tid decorator in Unified Logging may crash VM
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-12-04
- Updated: 2015-12-24
- Resolved: 2015-12-05
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 9 |
|---|
9 b99Fixed  |
Related Reports
|
Relates :
|
Description
To print the "tid" decorator for the current thread, Unified Logging uses Thread::current(). That will not work for the time before the TLS slot for the thread is initialized and after it is cleaned up. More robust would be to just use os::current_thread_id(), which should always work.