[
https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476214#comment-16476214
]
Alexey Goncharuk commented on IGNITE-8469:
------------------------------------------
[~Mmuzaf], can you please clarify which path leads to a duplicate call of
memory provider initialization?
If this is multiple invocations of {{ignite.cluster().active(true)}}, then we
should fix the activation process not to invoke the initialization twice. If
such a path exists, then your fix you will lead to concurrent threads accessing
freed memory and probably jvm crash.
I think we should throw an exception from {{initialize()}} anyway because
Ignite components generally are not reusable.
> 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)
