JDK-8173368 : Convert jdk.internal.misc.VM.latestUserDefinedLoader to use StackWalker
  • Type: Bug
  • Component: core-libs
  • Affected Version: 9
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-01-25
  • Updated: 2018-10-12
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
Blocks :  
JDK-8173898 - StackWalker.walk throws InternalError if called from a constructor invoked through reflection.
Relates :  
JDK-8170116 - Remove qualified exports from java.base to java.corba
Description
JVM_LatestUserDefinedLoader can be removed.  The stack walking can be done in java.

We should have java.io.ObjectInputStream and java.rmi.MarshalInputStream which are the two clients of jdk.internal.misc.VM.latestUserDefinedLoader to do the stack walking itself and remove  jdk.internal.misc.VM.latestUserDefinedLoader  entirely.  It's not a good practice to define an API to walk the stack to find the first user-defined loader.
Comments
See how JDK-8170116 is changing java.corba to stop depending on VM_LastUserDefinedLoader and use StackWalker instead.
25-01-2017
I doubt the current use of latestUserDefinedLoader is performance critical but it serves as good benchmark to tune the performance.
25-01-2017