You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Barry d'Hoine <ba...@amplexor.com> on 2017/05/16 13:34:36 UTC
Possible memory leak
Hello guys,
Our server is going out of memory due to insufficient metaspace. When analysing the heapdump that was created we also noticed in the Eclipse Memory Analyser that the is a possible memory leak suspect in org.apache.jackrabbit.oak.cache.CacheLIRS
The information shown by the application is:
One instance of "org.apache.jackrabbit.oak.cache.CacheLIRS" loaded by "org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5 @ 0x4c6efdb50" occupies 978,154,888 (63,79%) bytes. The memory is accumulated in one instance of "org.apache.jackrabbit.oak.cache.CacheLIRS$Segment[]" loaded by "org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5 @ 0x4c6efdb50".
Keywords
org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5 @ 0x4c6efdb50
org.apache.jackrabbit.oak.cache.CacheLIRS
org.apache.jackrabbit.oak.cache.CacheLIRS$Segment[]
We are using oak version 1.2.18, is this something to be alarmed about or is it a false positive?
Grtz,
Barry
Re: Possible memory leak
Posted by Barry d'Hoine <ba...@amplexor.com>.
Okay, after looking further into this it is indeed as you explained, thanks!
> On 17 May 2017, at 09:42, Chetan Mehrotra <ch...@gmail.com> wrote:
>
> On Tue, May 16, 2017 at 7:04 PM, Barry d'Hoine
> <ba...@amplexor.com> wrote:
>> org.apache.jackrabbit.oak.cache.CacheLIRS
>
> The CacheLIRS instance is a cache and hence would be referring to a
> big chunk of heap. Probably thats why MAT flags it. This alone does
> not confirm its a memory leak. The reachable size via this object
> should be closer to the cache size you have configured. If its much
> higher than configured cache size then that would need to be looked
> into
>
> What type of setup is this Document/Mongo or Tar?
>
>
>
> Chetan Mehrotra
Re: Possible memory leak
Posted by Chetan Mehrotra <ch...@gmail.com>.
On Tue, May 16, 2017 at 7:04 PM, Barry d'Hoine
<ba...@amplexor.com> wrote:
> org.apache.jackrabbit.oak.cache.CacheLIRS
The CacheLIRS instance is a cache and hence would be referring to a
big chunk of heap. Probably thats why MAT flags it. This alone does
not confirm its a memory leak. The reachable size via this object
should be closer to the cache size you have configured. If its much
higher than configured cache size then that would need to be looked
into
What type of setup is this Document/Mongo or Tar?
Chetan Mehrotra