-
Enhancement
-
Resolution: Unresolved
-
P3
-
None
-
Cause Known
Backtrace of a Throwable is currently captured by the VM built-in stack walking code. The StackWalker API can be used to replace the VM backtrace implementation. The VM built-in backtrace logic has been tuned for performance. The performance criteria should be identified and which benchmarks to compare the performance.
In addition, we need to look into a reliable way to fill in the backtrace during VM startup and also what to do when StackWalker throws any exception.
In addition, we need to look into a reliable way to fill in the backtrace during VM startup and also what to do when StackWalker throws any exception.
- relates to
-
JDK-8153123 Streamline StackWalker code
- Resolved
-
JDK-8001590 NPG: Footprint increase when running Jetty
- Closed
-
JDK-8153133 Thread.dumpStack() can use StackWalker
- Closed
-
JDK-8150778 Reduce Throwable.getStackTrace() calls to the JVM
- Resolved
-
JDK-8043814 JEP 259: Stack-Walking API
- Closed
1.
|
Performance measurement for enabling Throwable to use StackWalker | Open | Unassigned |