Hello Poonam,
On 05/12/18 1:56 AM, Poonam Parhar wrote: > Hello Jaikiran, > > Did you try collecting a heap dump and inspecting these ByteBuffers > that you suspect are holding on to non-heap memory? Looking at the GC > roots of these objects in the heap dump might shed some light as to > why these objects are not getting collected. My initial analysis (when I started this thread) turned out to be a false alarm, as you might have come to see based on my recent replies in this thread. Although the ByteBuffer usage was growing (and still does), it wasn't really leaking and based on more detailed analysis it was/is within the expected limits. So it wasn't really a issue with GC but more a kmem usage tracking issue with docker and the 3.x kernel version on CentOS. As I note in a recent reply to this thread, this got fixed in docker-ce, in a yet to be released version and our tests so far have shown that the fix is working. -Jaikiran _______________________________________________ hotspot-gc-use mailing list hotspot-gc-use@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
