[ https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472416#comment-16472416 ]
ASF GitHub Bot commented on IGNITE-8469: ---------------------------------------- GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3986 IGNITE-8469: release memory in case initialization multi times You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ignite-8469 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3986.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3986 ---- commit 38c0b2e3d26f3190f6d981ffa5f9a5862610f795 Author: Maxim Muzafarov <maxmuzaf@...> Date: 2018-05-11T18:23:28Z IGNITE-8469: release memory in case initialization multi times ---- > Non-heap memroy leak for calling cluster activation multi times > --------------------------------------------------------------- > > Key: IGNITE-8469 > URL: https://issues.apache.org/jira/browse/IGNITE-8469 > Project: Ignite > Issue Type: Bug > Components: persistence > Reporter: Maxim Muzafarov > Assignee: Maxim Muzafarov > Priority: Major > Fix For: 2.6 > > > Calling multiple time cluster (with enabled persistence and started client > nodes) activation {{ig3CB.cluster().active(true);}} leads to non-heap memory > leak. > Line > {{org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java:234}} > looks suspicious because of in case method > {{org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl#start}} > callled multi times (e.g. activate(true) called multi times) we lost info > about allocated regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)