JDK-8141239 : Throwable should use StackWalker API to capture the backtrace
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.lang
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2015-11-03
  • Updated: 2018-09-11
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8153123 - Streamline StackWalker code
Relates :  
JDK-8001590 - NPG: Footprint increase when running Jetty
Relates :  
JDK-8043814 - JEP 259: Stack-Walking API
Relates :  
JDK-8150778 - Reduce Throwable.getStackTrace() calls to the JVM
Relates :  
JDK-8153133 - Thread.dumpStack() can use StackWalker
Sub Tasks
JDK-8141532 :  
Performance measurement for enabling Throwable to use StackWalker - Open
Description
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.
Comments
Link to performance testing sensitive to throwable size.
24-12-2015