[
https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475512#comment-16475512
]
Maxim Muzafarov commented on IGNITE-8469:
-----------------------------------------
[~alex_pl],
As we've discussed, I've prepeared new test and using OperatingSystem MXBean to
mesuare virtual memory size before and after each unit-test in iteration. Can
you review my changes?
Global scenario for this leak is:
# Start topology with client nodes, presistence enabled
# Set active(true) for cluster. This activation should fail by some
circumstances (e.g. some locks exists)
# IgniteCacheDatabaseSharedManager started and onActive method called here.
New memory segment allocated for client node
# Set active(true) again. Activation successfull, non heap memory leak
introduced
> 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)
