JDK-8153123 : Streamline StackWalker code
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-03-30
  • Updated: 2016-04-28
  • Resolved: 2016-04-08
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.
JDK 9
9 b116Fixed
Related Reports
Relates :  
JDK-8154104 - Add test of StackFrameInfo.toStackTraceElement() in a named module
Relates :  
JDK-8043814 - JEP 259: Stack-Walking API
Relates :  
JDK-8141239 - Throwable should use StackWalker API to capture the backtrace
Description
After a fair amount of investigation, it looks like JDK-8141239 should wait for a later time.  However, the work yielded some footprint and code reduction changes we'd like to put into JDK 9:

* Refactor to streamline StackStreamFactory (no longer have separate classes[] and StackFrame arrays) and StackFrameInfo (use a StackTraceElement for storage, remove redundant methodName/fileName/lineNumber fields);

* Remove flags left in to ease benchmarking (-XX:+MemberNameInStackFrame, stackwalk.newThrowable), plus and related code

* Remove unneeded (for now) StackStreamFactory.StackTrace class and related code