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

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2014/02/04 08:32:09 UTC

[jira] [Commented] (OAK-1382) oak-core tests may run out of memory

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

Marcel Reutegger commented on OAK-1382:
---------------------------------------

Hmm, there is actually code in place to deal with DocumentNodeStore instances that are not disposed. The background thread only keeps a weak reference to the DocumentNodeStore. After a closer look at the dump it turns out the majority of memory is kept by DocumentMKConcurrentAddTest. The test creates a cluster with 16 DocumentMKs. Each instance has a default cache size of 256MB. The CacheLIRS eagerly initializes the internal data structures to avoid growing the hash tables later. This results in a quite high memory usage even if the caches are not full.

I'll reduce the cache sizes for the test.

> oak-core tests may run out of memory
> ------------------------------------
>
>                 Key: OAK-1382
>                 URL: https://issues.apache.org/jira/browse/OAK-1382
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>
> My oak-core build just ran out of memory. Quite a lot of memory is referenced from unused DocumentNodeStore instances, but are not garbage collected because the background thread associated with each store is still running. A test needs to dispose the store, which is missing in some of the tests.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)