Memory Leak in Kubernetes Client about kubernetes-client HOT 3 CLOSED

The first thing that I did was convert your example to just java 17 - removing the task executor override and using just a cached thread pool for running the jobs in main. At least for me after 10 minutes the memory usage just exhibited a normal pattern of gc, where the heap was not growing. So I suspect the issue is with using virtual threads for the task executor - can you cofirm this?

from kubernetes-client.

I disagree, I adjusted my code for using java 17 without virtual Threads like you did,

v2.zip

dump.zip

After running for 10 minutes with count 16 I see the client occupies now most of the heap, it will grow more and more. The absolute count of a few MB is not that big, but the relative count, in contrast to all the other classes gets absurd. Its the same pattern as with the virtual threads. When switching to 6.8.1 I don't see anything like this:

from kubernetes-client.

Ok, upping the thread count made the issue more appearent over a short interval. The problem is with the auto-closure logic - it's adding a task to ensure the informer is closed if the client is closed, but there's nothing cleaning that up when the informer is closed naturally.

from kubernetes-client.