By alashcraft
via blogs.microsoft.co.il
Published: Jul 14 2008 / 11:16
How do you determine whether the memory issue you seem to be experiencing is a .NET memory leak or a native memory leak? Why is it even important? It's the first question I as a consultant would ask you if we were to talk over the phone regarding a high-memory problem you've having. It's extremely important because in most of the cases it narrows the scope of the problem and facilitates bringing the appropriate people, tools and resources for focusing on the task at hand.
Add your comment