You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/02/19 12:07:20 UTC

[jira] [Commented] (SLING-3400) Sling holds resource providers after they have been unregistered

    [ https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905084#comment-13905084 ] 

Carsten Ziegeler commented on SLING-3400:
-----------------------------------------

[~lbyrum] Can you confirm / verify that this is caused by long running resource resolvers? Thanks

> Sling holds resource providers after they have been unregistered
> ----------------------------------------------------------------
>
>                 Key: SLING-3400
>                 URL: https://issues.apache.org/jira/browse/SLING-3400
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Laurie byrum
>            Assignee: Carsten Ziegeler
>             Fix For: Resource Resolver 1.1.0
>
>
> We have been checking to see what class references leak after our code has been unloaded. One thing that leaks is our resource provider which is being held in Sling's Resource Resolver. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)