How to trap a memory leak?

[james]

Hello,

I'm doing some longer running tests on my application, and it looks like
there is a memory leak... If I run it, it is fine for a few hours, but if I
check next day it's using 300Mb of RAM or so!

How do I go about tracking down what part of my code is causing this? Is
there a way of seeing what objects haven't been disposed of etc?

 

[Vadym Stetsyak]

Hello, james!

j> I'm doing some longer running tests on my application, and it looks like
j> there is a memory leak... If I run it, it is fine for a few hours, but
j> if I check next day it's using 300Mb of RAM or so!

You can use profiler to detect what objects are not collected by GC.
ClrProfiler is a good start
( http://www.microsoft.com/downloads/...52-d7f4-4aeb-9b7a-94635beebdda&displaylang=en )

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

 

[Guest]

Though the suggested CLRProfiler will help you to handle the situation,
please give a look at this link to understand the memory leaking in .NET.

http://himabinduvejella.blogspot.com/2006/06/memory-leaks-in-managed-code.html

What do you say?

 

[james]

Though the suggested CLRProfiler will help you to handle the situation,
please give a look at this link to understand the memory leaking in .NET.

http://himabinduvejella.blogspot.com/2006/06/memory-leaks-in-managed-code.html

Looks helpful, thanks