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...aged-code.html
What do you say?
--
Every thing is perfect, as long as you share!!!
"james" wrote:
Quote:
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?
>
>
>
