You are creating a Universal Windows Platform (UWP) app by using Microsoft Visual Studio 2015.
You discover that the app uses more memory than expected. You suspect that a method named Method1 is consuming most of the memory.
You need to identify the changes in memory that are a direct result of executing Method1.
What should you do?
A.
From Visual Studio, set a breakpoint on the method and immediately after the method.Fromthe Diagnostic Tools, clickTake Snapshotwhen each breakpoint is hit.
B.
From the Debug tab in Visual Studio, clickStart Diagnostic Tools Without Debugging,selectApplication Timeline,and then clickStart.
C.
From the Windows Performance Analyzer, record the memory consumption.
D.
From Windows Performance Monitor, create a Data Collector Set (DCS). Start the DCS, run the app, and then stop the DCS.
Explanation:
Find memory leaks and inefficient memory while you’re debugging with the debugger-integrated Memory Usage diagnostic tool. The Memory Usage tool lets you
take one or more snapshots of the managed and native memory heap.
Although you can collect memory snapshots at any time in the Memory Usage tool, you can use the Visual Studio debugger to control how your application executes
while investigating performance issues. Setting breakpoints, stepping, Break All, and other debugger actions can help you focus your performance investigations on
the code paths that are most relevant.https://msdn.microsoft.com/en-us/library/mt125494.aspx