-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 11, 12, 13
-
Component/s: hotspot
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8282176 | 11.0.16-oracle | Joakim Nordström | P4 | Resolved | Fixed | b01 |
| JDK-8223535 | 11.0.4 | Yasumasa Suenaga | P4 | Resolved | Fixed | b03 |
| JDK-8251222 | openjdk8u272 | Yasumasa Suenaga | P4 | Resolved | Fixed | b02 |
JFR did not collect call stacks when MaxJavaStackTraceDepth is set to zero.
How to reproduce:
1. Pass some arguments to `java`
-XX:StartFlightRecording=filename=test.jfr,settings=profile -XX:MaxJavaStackTraceDepth=0
2. Run application
3. Open flight record (test.jfr) on JMC
4. Check call stack on "Method Profiling" window
This bug is similar toJDK-7179701.
How to reproduce:
1. Pass some arguments to `java`
-XX:StartFlightRecording=filename=test.jfr,settings=profile -XX:MaxJavaStackTraceDepth=0
2. Run application
3. Open flight record (test.jfr) on JMC
4. Check call stack on "Method Profiling" window
This bug is similar to
- backported by
-
JDK-8223535 JFR did not collect call stacks when MaxJavaStackTraceDepth is set to zero
-
- Resolved
-
-
JDK-8251222 JFR did not collect call stacks when MaxJavaStackTraceDepth is set to zero
-
- Resolved
-
-
JDK-8282176 JFR did not collect call stacks when MaxJavaStackTraceDepth is set to zero
-
- Resolved
-
- relates to
-
JDK-7179701 MaxJavaStackTraceDepth of zero is not handled correctly/consistently in the VM
-
- Resolved
-