[
https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906786#comment-13906786
]
Carsten Ziegeler commented on SLING-3400:
-----------------------------------------
It seems this is really caused by long running resource resolvers. They hold a
reference to the used resource provider for as long as the resource resolver
exists
> 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)
