JDK-8141538 : Make DynamicLinker specific to a Context in Nashorn
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: jdk.nashorn
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2015-11-05
  • Updated: 2024-10-04
  • Resolved: 2015-11-09
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 b93Fixed
Related Reports
Blocks :  
JDK-8141550 - Introduce a command line option instead of nashorn.unstable.relink.threshold system property
Relates :  
JDK-8229011 - Leak (.invoke.LambdaForm, invoke.BoundMethodHandle)
Relates :  
JDK-8198540 - Dynalink leaks memory when generating type converters
Description
Currently, DynamicLinker is a static singleton in Nashorn. It should be specific to a Context instead.

A DynamicLinker instance can incorporate exported linkers from other language runtimes, discovered through ServiceLoader mechanism on a class loader. Context has such a class loader, its appLoader. Therefore, DynamicLinker should be local to a Context and constructed through a factory that uses the Context's appLoader for discovery of exported linkers.

This will allow Nashorn to coöperate with other language runtimes present in the appLoader's classpath
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/nashorn/rev/e08b29ee795e User: lana Date: 2015-11-18 23:53:17 +0000
18-11-2015
URL: http://hg.openjdk.java.net/jdk9/dev/nashorn/rev/e08b29ee795e User: attila Date: 2015-11-09 13:04:50 +0000
09-11-2015