NET Memory leak analysis?

Memory leak diagnostics is a built-in feature of the Microsoft CRT, the _CrtDumpMemoryLeaks() function provides a report. Using it requires writing unit tests in native code so that you can enable the debug allocator to make this function work. Which in turn requires that you have to source code for this unmanaged code so you can enable the debug allocator with the crtdbg.

H header file and can build the unit test. Essential guide is here .

If you want a real memory profiler tool, have a look at http://memprofiler.com/support.aspx. By far one of the best tools for memory leaks that I have ever used. .

NET interops with unmanaged code all over the place. Just because the leak appears in unmanaged code doesn't mean that you don't have a held-reference issue in your code somewhere. If you provide some details of why you think you have a memory leak issue and more about your solution perhaps we can offer more solutions.

Setting a variable to null doesn't magically force the garbage collector to be invoked. GC'ing is an expensive process and should be avoided unless absolutely necessary, hence the collector only runs as and when it's scheduled to or if there is a need.

This is normal. The garbage collector runs on it's own time, as needed. The fact that it returns to normal when the garbage collector is forced means there's no leak or permanent references keeping things around.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.