When diagnosing a memory leak in a .NET application, what does it mean if the working set is large but the data on the heap is small?

Viewed 62

I have an application running in Kubernetes that seems to have a memory leak, after running for some time Kubernetes will scale out to the max count of instances, and terminate them when they reach the max memory.

I have installed some profiling tools and found that the 'Working set' is large, taking up 1.7gb, but when I open a dump of the memory I see that the application is only using about 44mb. What can I do next to see where all the memory is going?

enter image description here

0 Answers
Related