{"id":453,"date":"2014-04-16T09:30:00","date_gmt":"2014-04-16T09:30:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudio\/2014\/04\/16\/enhancements-to-debugging-and-profiling-in-visual-studio-2013-update-2\/"},"modified":"2022-09-30T15:24:39","modified_gmt":"2022-09-30T22:24:39","slug":"enhancements-to-debugging-and-profiling-in-visual-studio-2013-update-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/enhancements-to-debugging-and-profiling-in-visual-studio-2013-update-2\/","title":{"rendered":"Enhancements to Debugging and Profiling in Visual Studio 2013 Update 2"},"content":{"rendered":"

Less than a year ago, I gave you a quick overview of the many investments we made to debugging and profiling in Visual Studio 2013 RTM<\/a> and got some great feedback from you about what we\u2019d done. Now, with Visual Studio 2013 Update 2 RC<\/a> available for download<\/a>, I wanted to run you through the enhancements we have made since last summer. We\u2019ve done a lot, so this summary post mostly links to other posts.<\/p>\n

I wanted to talk about two of the larger efforts we\u2019ve made first: the Performance and Diagnostics hub<\/a> (from where you can run tools such as the HTML UI Responsiveness tool<\/a>, XAML UI Responsiveness tool<\/a>, and Energy Consumption tool<\/a>) and the ability to analyze .NET memory dumps<\/a>.<\/p>\n

With the Performance and Diagnostics hub<\/strong>, you now have the capability to run more than one tool at a time and look at the results in a combined view<\/a>, so that you can cross-correlate activity from one tool with activity from another (e.g. “I can see that while my CPU was doing X, my UI was doing Y”). We\u2019ve also introduced a new CPU Usage tool<\/a>, for seeing where your .NET, C++, and JavaScript functions are using the CPU. And finally, we\u2019ve added a Memory Usage tool<\/a> for your .NET and C++ code to complement the JavaScript Memory tool<\/a> we shipped previously.<\/p>\n

\"\"<\/a><\/p>\n

Another large investment for VS2013 was the .NET memory dump tool<\/strong>, which includes the capability to inspect values of objects from the dump file<\/a>. You can use this feature to investigate memory leaks with your Azure Web Site<\/a> (new with Update 2 is the diffing capability for .diagsession files).<\/p>\n

There are several other notable features<\/strong>, two of which I\u2019ll call out:<\/p>\n