[
https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105720#comment-15105720
]
Robert Munteanu commented on SLING-5205:
----------------------------------------
For the sake of being complete, here's a screenshot of the path to the GC root
for the leaking resource provider [^shortest-path.png]
> Check for potential memory leaks
> --------------------------------
>
> Key: SLING-5205
> URL: https://issues.apache.org/jira/browse/SLING-5205
> Project: Sling
> Issue Type: Sub-task
> Components: ResourceResolver
> Reporter: Carsten Ziegeler
> Assignee: Robert Munteanu
> Fix For: Resource Resolver 1.3.0
>
> Attachments: duplicate-mongodb-resource-provider.png,
> shortest-path.png
>
>
> With long running resource resolvers and provider dynamically being
> registered, we need to check that we don't hold too strong references on the
> providers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
