You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Aleksandrov (JIRA)" <ji...@apache.org> on 2018/05/03 08:32:00 UTC
[jira] [Commented] (IGNITE-7918) Huge memory leak when data
streamer used together with local cache
[ https://issues.apache.org/jira/browse/IGNITE-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462103#comment-16462103 ]
Andrey Aleksandrov commented on IGNITE-7918:
--------------------------------------------
[~dpavlov] Thank you. Changes that you saw are results of fixing code style issues and merging with master that I did to re-run failed suites.
> Huge memory leak when data streamer used together with local cache
> ------------------------------------------------------------------
>
> Key: IGNITE-7918
> URL: https://issues.apache.org/jira/browse/IGNITE-7918
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.3
> Reporter: Zbyszek B
> Assignee: Andrey Aleksandrov
> Priority: Major
> Fix For: 2.6
>
> Attachments: Demo.java, MemLeak-Ignite.png, MemLeak-Ignite.txt
>
>
> Dear Igniters,
> We observe huge memory leak when data streamer used together with local cache.
> In the attached demo producer produces local cache with single binary object and passes this to the queue. Consumer picks up the cache from the queue, constructs different binary object from it, adds it to global partitioned cache and destroys local cache.
> This design causes a significant leak - the whole heap is used within minutes (no matter if this is 4G or 24G).
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)