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 2023/05/24 06:21:00 UTC

[jira] [Commented] (OAK-10259) oak-core tests running out of memory

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

Marcel Reutegger commented on OAK-10259:
----------------------------------------

Proposed change in PR https://github.com/apache/jackrabbit-oak/pull/953

Clearing inline mocks at the end of a security test shows much lower memory usage. Also note, that I had to make changes to some tests. E.g. LoginContextProviderImplTest did not remove security providers it adds during a test, which then caused failures later when the mocked provider was cleared. 

> oak-core tests running out of memory
> ------------------------------------
>
>                 Key: OAK-10259
>                 URL: https://issues.apache.org/jira/browse/OAK-10259
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: continuous integration, core
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>
> Recently tests for oak-core were running out of memory on Jenkins. Analyzing a heap dump showed majority of heap (300 MB) retained by Mockito. It looks like this is related to https://github.com/mockito/mockito/pull/1619 and with OAK-10173 we enabled mock-maker-inline.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)