[
https://issues.apache.org/jira/browse/SLING-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298306#comment-14298306
]
Felix Meschberger commented on SLING-3859:
------------------------------------------
To clarify: The ResourceResolver implementation
[ResourceResolverImpl|http://svn.apache.org/repos/asf/sling/trunk/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverImpl.java]
implements a {{finalize()}} method ensuring it is closed once not referenced
any longer. This mitigates the problem.
The issue might arise, though, is if there are so many temporary resolvers
created and kept that they cannot be collected in time and thus fill up memory.
> ResourceResolver from JcrItemAdapterFactory is not closed
> ---------------------------------------------------------
>
> Key: SLING-3859
> URL: https://issues.apache.org/jira/browse/SLING-3859
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.3.6
> Reporter: Carsten Ziegeler
> Fix For: JCR Resource 2.4.2
>
>
> Whenever a node or property is adapted to something a new resource resolver
> is created with the same user session as the node is from. However, this
> resolver is never closed and therefore is a potential memory leak
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
