title: memory leak in .net application, debugdiag analysis is not giving GC details
body: <p>We have a asp.net website hosted on IIS and If my application runs for more than a day,it uses more than 4 GB and stays like that.Currently we have a set a recycling as a work around. I am in the process of finding out the root cause of the leak using debugdiag.</p>
  
  <p><strong>Edit:</strong></p>
  
  <p>I tried to use windbg by following <a href="http://www.diaryofaninja.com/blog/2014/03/20/investigating-aspnet-memory-dumps-for-idiots-like-me" rel="nofollow noreferrer">this</a> but manual analysis did not really help.But I found out that debugdiag's automated analysis can tell you which .net obejcts are consuming most objects .Following these <a href="https://msdn.microsoft.com/en-us/library/aa577477.aspx" rel="nofollow noreferrer">articles</a> and this from Microsoft</p>
  
  <p>Was expecting to see .net information like this <a href="https://i.stack.imgur.com/sgVPy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/sgVPy.png" alt=".net information in the dumps"></a> but instead I got the error <strong>"Your browser settings are currently prohibiting this report's scripts from running"</strong></p>
  
  <p>I followed <a href="https://blogs.msdn.microsoft.com/tess/2010/01/14/debugging-native-memory-leaks-with-debug-diag-1-1/" rel="nofollow noreferrer">this</a> and <a href="https://blogs.msdn.microsoft.com/benjaminperkins/2016/02/01/analyze-a-memory-dump-using-the-debug-diagnostic-tool/" rel="nofollow noreferrer">this</a> article but the analysis is not giving much details on .NET and this is a pure .NET application.I was expecting to see Memory consuming .NET objects and GC details etc.</p>