You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2015/06/08 16:10:00 UTC

[jira] [Resolved] (SLING-4783) The JavaScript scripting engine can generate classloader leaks

     [ https://issues.apache.org/jira/browse/SLING-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu resolved SLING-4783.
---------------------------------
    Resolution: Fixed

Fixed in [r1684189|https://svn.apache.org/viewvc?view=revision&revision=r1684189].

> The JavaScript scripting engine can generate classloader leaks
> --------------------------------------------------------------
>
>                 Key: SLING-4783
>                 URL: https://issues.apache.org/jira/browse/SLING-4783
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: Scripting JavaScript 2.0.18
>
>         Attachments: heap dump analysis.png
>
>
> The implementation of the JavaScript scripting engine, based on Rhino, can lead to classloader leaks due to Rhino's {{ClassCache}} if the used classloader for loading objects is a {{DynamicClassLoader}}. The cache is used by default to cache object translation from JavaScript to Java and generally outlives the objects it stores, holding a hard reference to them.
> Disabling the cache is not a solution as synthetic tests proved that the execution of JavaScript code had increased two times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)