[bob1029]

To be fair, there is an entire class of GC/memory problems that aren't technically a leak but manifest in effectively the same way.

The most common one I see is LOH (Large Object Heap) fragmentation. When objects are promoted to the LOH the runtime doesnt bother with moving them around anymore. There is a way to explicitly compact the LOH but it can be a non-starter for a lot of applications.

https://learn.microsoft.com/en-us/dotnet/api/system.runtime....

I've once exposed this as a button that a customer's IT department could click whenever they received an alert on memory utilization. The actual solution would have been to refactor the entire product to not pass gigantic blobs around all the time, but that wasn't in the cards for us.