>>>Hello,
>>>I'm trying to track down a memory leak in an ASP.NET application, and it has brought me to question how User Controls are disposed. Since we don't explicitly dispose of them, I'm assuming it's part of the ASP.NET page lifecycle, is that correct?
>>>
>>
>>Yes, they'll get disposed of by the framework. Do you happen to have any external event handlers (handlers for things other than controls)? If so, you might want to check to make sure you're removing them.
>
>Nope, not too much special in my case. Which is why this memory leak is maddening.

Download the demo version of Redgate's Memory Profiler: http://www.red-gate.com/products/ants_memory_profiler/index.htm

It does a nice job of displaying objects which aren't being disposed up. You basically attach it to your app and then run it a while (through the areas you think are causing the leak). It will show a graph of objects which are undisposed which you can follow up to the code that created them.

The demo works for like 14 days which might be enough time to find the leak.