memory leak

[michaelw]

My application on discount asp.net appears to have a memory leak. I have reviewed my code to make sure I am discarding all data objects, but the leak still persist. How do I go about detecting where the leak is occuring?

[bruce]

Memory leak is one of the tricky thing to debug

I suggest

1) Run your application on a local computer
2) use perfmon or task manager to track the memory usage of the process
3) Step through your application in debug mode and see where memory usage jumps


[b]quote:Originally posted by michaelw

My application on discount asp.net appears to have a memory leak. I have reviewed my code to make sure I am discarding all data objects, but the leak still persist. How do I go about detecting where the leak is occuring?
</blockquote id="quote"></font id="quote">

[burgsnetcom]

I am still getting this viewstate timeout and my form isn't even that big.

What is the timeout setting?

Is there something I can add into my page to refresh and prevent this?

Thanks in advance,
Steve

Burg
---------
We have enough youth, how about a fountain of Smart?

[rocer]

Maybe somebody knows, I am confused now.

One of the features of .NET languages is automatic garbage collection. (actually it is a low priority process executed by the CLR).

This process is supposed to detect memory leaks and it returns the memory to the heap when it knows the system is running out of memory. Unless you have a reference to an object, the object won't be garbage collected, but otherwise?

You don't even have to invoke the object destructor as the garbage collector does it for you when needed.

How come users can still have a memory leaks? Thanks.