ProfilerThreadDump

Revision as of 15:17, 9 October 2015 (view source) Jis (Talk | contribs) m ← Older edit		Current revision as of 17:01, 2 November 2015 (view source) Jis (Talk | contribs) m
(7 intermediate revisions not shown)
Line 1:		Line 1:
	=Getting Thread Dump=		=Getting Thread Dump=
-	This page describes getting a threads dump from the profiled application.	+	This page describes getting a thread dump from the profiled application.
-	The thread dump can be taken whenever the profiler is connected to a process, no matter what the current profiling mode is. However, to take a thread dump with minimal overhead on the profiled application, start a '''Telemetry''' profiling session - see [[ProfilerTelemetry|Profiling Telemetry]].	+	[[File:tdump.png]]
-	Once the profiling session runs, the threads dump can be taken by clicking the '''Thread dump''' action in '''Process section''' of the Profiler window toolbar.	+	The thread dump can be taken whenever the profiler is connected to a process (see [[ProfilerFirstSession|First Profiling Session]] for details on starting a profiling session), no matter what the current profiling mode is. However, to take a thread dump with minimal overhead on the profiled application, start a '''Telemetry''' profiling session - see [[ProfilerTelemetry|Profiling Telemetry]].
		+	Once the profiling session runs, the thread dump can be taken by clicking the '''Thread dump''' button in Process section of the Profiler window toolbar or using the main IDE menu | Profile section.
		+
		+	Eventually the thread dump is opened in a separate window. It displays call stacks of each thread at the point of creating the dump, with '''links to source code''' of the methods.
	__NOTITLE__		__NOTITLE__
	__NOTOC__		__NOTOC__

---

Current revision as of 17:01, 2 November 2015

Getting Thread Dump

This page describes getting a thread dump from the profiled application.

The thread dump can be taken whenever the profiler is connected to a process (see First Profiling Session for details on starting a profiling session), no matter what the current profiling mode is. However, to take a thread dump with minimal overhead on the profiled application, start a Telemetry profiling session - see Profiling Telemetry.

Once the profiling session runs, the thread dump can be taken by clicking the Thread dump button in Process section of the Profiler window toolbar or using the main IDE menu | Profile section.

Eventually the thread dump is opened in a separate window. It displays call stacks of each thread at the point of creating the dump, with links to source code of the methods.

• This page was last modified on 2 November 2015, at 17:01.
• This page has been accessed 4,318 times.