-
Enhancement
-
Resolution: Fixed
-
P3
-
15
-
b12
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8258691 | 13.0.6 | Ekaterina Vergizova | P3 | Resolved | Fixed | b04 |
JDK-8254625 | 11.0.10-oracle | David Buck | P3 | Resolved | Fixed | master |
JDK-8255052 | 11.0.10 | Denghui Dong | P3 | Resolved | Fixed | b01 |
JDK-8273769 | openjdk8u322 | Yi Yang | P3 | Resolved | Fixed | b01 |
The ThreadStart event is committed in a new thread, so users can't know the location of where the thread starts. The stack trace can however be taken in the parent thread. The stack trace is helpful when diagnosiing thread leaks.
- backported by
-
JDK-8254625 JFR: Include stack trace in the ThreadStart event
- Resolved
-
JDK-8255052 JFR: Include stack trace in the ThreadStart event
- Resolved
-
JDK-8258691 JFR: Include stack trace in the ThreadStart event
- Resolved
-
JDK-8273769 JFR: Include stack trace in the ThreadStart event
- Resolved
- relates to
-
JDK-8239886 Minimal VM build fails after JDK-8237499
- Resolved
(2 links to)