ProfilerThreadDump

(Difference between revisions)
m
m
 
(2 intermediate revisions not shown)
Line 2: Line 2:
This page describes getting a thread dump from the profiled application.
This page describes getting a thread dump from the profiled application.
 +
[[File:tdump.png]]
-
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]].
+
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.
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 calls.
+
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.

File:tdump.png

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.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo