[jira] [Comment Edited] (SLING-5205) Check for potential memory leaks

["Robert Munteanu (JIRA)" <ji...@apache.org>]

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

Robert Munteanu edited comment on SLING-5205 at 1/18/16 3:41 PM:
-----------------------------------------------------------------

After changing the OSGi config of the MongoDB provider, the old provider is still retained. I've validated this with two heap dumps ( see [^duplicate-mongodb-resource-provider.png] ).


was (Author: rombert):
After changing the OSGi config of the MongoDB provider, the old duplicate is still retained. I've validated this with two heap dumps ( see [^duplicate-mongodb-resource-provider.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
>             Fix For: Resource Resolver 1.3.0
>
>         Attachments: duplicate-mongodb-resource-provider.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)