I often get questions about debugging native memory leaks. In other words, cases where you have high memory usage in your application but you can see that .net memory usage is not all that high. Recently I was helping out on such a case and this post details both generally how you go about troubleshooting these issues as well as what troubleshooting steps we went through in this particular case. Essentially you would go through these steps to troubleshoot a native memory leak: 1. Find out if your memory usage / leak is mostly .net memory or native memory 2. If it is native memory that is “leaking”, use a tool like debug diag 1.1. to track allocations and deallocations 3. Look at the main allocators and the stacks associated with the biggest…(read more)
January 14th, 2010 → 1:21 pm @ Editor
0