We are currently investigating a memory leak in our ASP.NET API application but we are seeing some strange results when we analyse memory dumps.
We are obtaining the dumps by remoting onto the box during testing and identifying the w3wp process that is using the most memory (we have multiple app pools on the box so there are multiple w3wp processes but one of them is using significantly more than the others) then using Task Manage to create a dump file.
Typically the dump files are over 1GB but when we analyse them using dotMemory it says the total object space is ten's of MBs.
Obviously the whole dump isn't going to be .NET memory usage but that seems like a big disparity. Could this caused by how we are taking the dumps? What else could be using the memory?