ProfilerHeapDump
(Difference between revisions)
(Created page with '=Getting Heap Dump= __NOTITLE__ __NOTOC__') |
m |
||
| Line 1: | Line 1: | ||
=Getting Heap Dump= | =Getting Heap Dump= | ||
| + | This page describes getting a heap dump from the profiled application. | ||
| + | The heap dump can be taken whenever the profiler is connected to a process, no matter what the current profiling mode is. However, to take a heap dump with minimal overhead on the profiled application, start a '''Telemetry''' profiling session - see [[ProfilerTelemetry|Profiling Telemetry]]. | ||
| + | |||
| + | Once the profiling session runs, the heap dump can be taken by clicking the '''Heap dump''' button in Process section of the Profiler window toolbar. | ||
| + | |||
| + | Eventually the heap dump is opened in the heap viewer in a separate window. | ||
| + | |||
| + | '''''Note:''' Taking heap dumps is not available for remote processes.'' | ||
__NOTITLE__ | __NOTITLE__ | ||
__NOTOC__ | __NOTOC__ | ||
Revision as of 15:33, 9 October 2015
Getting Heap Dump
This page describes getting a heap dump from the profiled application.
The heap dump can be taken whenever the profiler is connected to a process, no matter what the current profiling mode is. However, to take a heap dump with minimal overhead on the profiled application, start a Telemetry profiling session - see Profiling Telemetry.
Once the profiling session runs, the heap dump can be taken by clicking the Heap dump button in Process section of the Profiler window toolbar.
Eventually the heap dump is opened in the heap viewer in a separate window.
Note: Taking heap dumps is not available for remote processes.
