Re: Reusing Ignite-Marshaller leads to a Memory-Leak

2017-01-22 Thread Peter Schmitt
Hi Denis, I think I've found the issue. Ignite skips references to Ignite-Caches. Moving away from the Ignite-Cache, but using the Ignite-Marshaller caused the issue. So it isn't an issue Ignite can prevent. Removing those references did it. Thanks for listening, Peter 2017-01-22 6:15 GMT+01:0

Re: Reusing Ignite-Marshaller leads to a Memory-Leak

2017-01-21 Thread Denis Magda
Sorry, didn’t pay attention that the size of every object is 1 KB. Then I would suggest to share your test/heap dump to see what happens. — Denis > On Jan 21, 2017, at 9:10 PM, Denis Magda wrote: > > Hello Peter, > > This behavior is expected. Look, you serialize 2000 objects * 1000 KB which

Re: Reusing Ignite-Marshaller leads to a Memory-Leak

2017-01-21 Thread Denis Magda
Hello Peter, This behavior is expected. Look, you serialize 2000 objects * 1000 KB which gives ~ 2 GB in total. After that you hold the references to these objects by putting them into an ordinary hash map. The objects will not be removed from the heap until the map keeps them. One the other s

Reusing Ignite-Marshaller leads to a Memory-Leak

2017-01-21 Thread Peter Schmitt
Hello Ignite-Community! I would like to use the Marshaller from Ignite for de-/serialising objects. I would like to re-use it, because it's very fast and I'm using Ignite anyway. I tried it with: //every thread gets the Marshaller via: GridKernalContext ctx = ((IgniteKernal) ignite).context(); M