title: Can CLR Profiler be used to find memory leaks
body: <p>My .NET application has memory leak. Few people seem to recommend using CLR Profiler for this pupose I am a bit lost on the idea. To me in order to find a memory leak, tool should compare two memory states that can give you statistics like growth in objects between two states. So in my mind, if a tool cannot compare two (or more) memory states, it cannot be used for detecting memroy leak. Obviously things like performance counters is bit different concept where you can trend the memory usage.</p>
  
  <p>So my question is really if someone can explain how exactly CLR Profiler can be used to detect memory leaks?  </p>