[ https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677009#comment-16677009 ]
Max Shonichev commented on IGNITE-8469: --------------------------------------- ok, here are final results with 100 iterations activate/deactivate scenario: without fix, total process memory is slowly increasing approx each 20 iterations: {noformat} 10298776 ... 10283356 10284384 ... 10286432 {noformat} with fix, total process memory is changed a little first few runs, than remains constant all 90+ iterations {noformat} 14501520 10099096 10232216 10232216 10297752 ... 10297752 {noformat} so, it seems, that this scenario also shows memory leak fixed, [~Mmuzaf], please confirm > Non-heap memory 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.7 > > > 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)