You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/09/26 17:45:44 UTC
[jira] Closed: (SLING-676) Rhino context not properly shutdown when
bundle is stopped
[ https://issues.apache.org/jira/browse/SLING-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-676.
-----------------------------------
Resolution: Fixed
Checking Rev. 699373 completes this fix.
> Rhino context not properly shutdown when bundle is stopped
> ----------------------------------------------------------
>
> Key: SLING-676
> URL: https://issues.apache.org/jira/browse/SLING-676
> Project: Sling
> Issue Type: Bug
> Components: Scripting JavaScript (Rhino)
> Affects Versions: Scripting JavaScript 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Scripting JavaScript 2.1.0
>
>
> Upon shutdown of the scripting/javascript bundle, the Rhino context is not properly shutdown thus leaving traces in the system and preventing correct garbage collection the classes. Most notably the following issues occurr in the factory:
> * The Context used to create the root scope is never exited (this leaves a thread-local behind)
> * The Debugger window is not properly closed (this leaves traces in the AWT behind)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.