Поделиться через

DebugDiag 2 Update 2 is now available

  • Статья

 

The DebugDiag development team is back with a new release!  We are very excited to announce the general availability of DebugDiag 2 Update 2.

A number of fixes and features are included in this release.  A summary of these enhancements is as follows:

 

      • Resolved issue with High CPU in dbghost due to exception monitoring when the target throws high rate of exceptions
      • Resolved issue with memory leak in dbghost due to bug in sos.dll
      • Added Autoupdate security enhancements
      • Fixes in leaktrack native memory tracking
      • Resolved Breakpoint issue against .net 4.6 targets
      • A number of exceptions during analysis are resolved
      • New report format with greatly improved organization and filtering
      • Introduced latest Microsoft.Diagnostics.Runtime.dll
      • Added support for analysis of .net 4.6 targets
      • A number of new analysis checks are added
      • …etc.

 

The release is available here:  https://www.microsoft.com/en-us/download/details.aspx?id=49924

 

Please email dbgdiag at Microsoft dot com for issues

 

Thank you

 

The DebugDiag Development Team

Comments

  • Anonymous
    November 17, 2015
    The comment has been removed

  • Anonymous
    November 17, 2015
    I miss my name at error information. Tanks

  • Anonymous
    November 17, 2015
    I was trying Rule Builder Designer from the Help Document. In Using the RuleBuilder section it says " The same way, add another argument and name it ManagedException and set the type to Microsoft.Diagnostics.Runtime.ClrException."  However I don't see any ClrException type if I search for the type in References window. What am I missing ?

  • Anonymous
    November 18, 2015
    Great! Thanks for your efforts guys!!!

  • Anonymous
    November 27, 2015
    I am getting the same error as Luiz

  • Anonymous
    December 03, 2015
    Can't get "Monitor for leaks" to work with Windows store apps.  Normal desktop apps work fine.  Tried with the built-in windows store apps so not specific to my app. Any ideas?

  • Anonymous
    January 31, 2016
    The comment has been removed

  • Anonymous
    February 02, 2016
    Thanks for DebugDiag, it's fantastic! But I'm also finding it very slow to analyze: I'm analyzing 4 minidumps plus a full dump (default output) of a .net web application. Minidumps are 3mb, full is 740mb. It's been running for over 3 hours now but Debug.Diag.Analysis.exe is only using around 45mb ram, 5% cpu, and my disk utilization is very low ... so I wonder what it's doing that is taking so long and if there's any way I can speed things up? I'm on a surface pro 3, running win 10 pro. Not the fastest machine around but i5 cpu, SSD and 8GB ram and it's not doing much else except waiting for this debugdiag analysis to finish. Any suggestions? thanks, Rory