[ 
https://issues.apache.org/jira/browse/IGNITE-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zbyszek B updated IGNITE-7918:
------------------------------
    Description: 
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).

 

 

  was:
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 it takes within minutes 
(no matter if this is 4G or 24G).

 

 


> 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
>            Priority: Blocker
>         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)

Reply via email to