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

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/01/18 16:39:39 UTC

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

     [ https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-5205:
-----------------------------------
    Attachment: 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)