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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2016/05/25 09:30:12 UTC

[jira] [Commented] (OAK-3109) OOME in tarkmk standby tests

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

Alex Parvulescu commented on OAK-3109:
--------------------------------------

merged (because of OAK-3007) to 1.2 branch with r1745464.

> OOME in tarkmk standby tests
> ----------------------------
>
>                 Key: OAK-3109
>                 URL: https://issues.apache.org/jira/browse/OAK-3109
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: tarmk-standby
>            Reporter: Michael Dürig
>            Assignee: Alex Parvulescu
>              Labels: candidate_oak_1_0
>             Fix For: 1.4, 1.3.4, 1.2.16
>
>
> Running the tarmk-standby ITs results in an OOME when running with the new string cache from OAK-3007. Looking at the heap dump I see many {{SegmentTracker}} instances around, which leads me to think that the test setup might have a leak somewhere. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)