Few days ago I was looking to find if I can spy may dot net application to get what's doing CLR under the hood. Then I had found an amazing tool, CLR profiler. I think most people doesn't know about it or are not used to with it. I have found the tool amazing for identifying some issues like memory leak. There are two versions of CLR profiler: for .net version 1.1 and version 2.0.
With this tool we can easily find the following three issues:
1. Is our application allocating too much memory?
2. Which objects are staying in memory too much time?
3. If we are holding memory but not relasing properly.