Fully featured low overhead profiler for Java EE and Java SE platforms.
Easy-to-use performance and memory .NET profiler for Windows, Linux and macOS.
Secure and easy profiling in cloud, containers and clustered environments.
Performance monitoring and profiling of Jenkins, Bamboo, TeamCity, Gradle, Maven, Ant and JUnit.

Exception profiling

"Exceptions" tab shows exceptions which were thrown in the profiled application.

exceptions tab

Exceptions may be grouped by their exception class or by thread in which they occurred. Selecting an exception in the upper table allows viewing the exception stack traces.

Checkbox "Show exceptions thrown and caught inside filtered methods" enables to filter out exceptions which have been thrown and caught in methods of library classes. By default, the checkbox is unselected, as such kind of exceptions are usually of no interest when profiling your application.

You can clear recorded exceptions with the help of corresponding toolbar button:

You can compare exception statistics of two snapshots with the help of File | Compare Snapshot with....

Start/stop exception profiling

Exception profiling helps discovering performance issues and logic errors. In most cases, there is no significant overhead of collecting this information.

However, it makes sense to disable it in production Java servers in order to ensure minimum profiling overhead.

Whether the exception profiling is enabled by default depends on the JVM and can be adjusted with the following startup options:

  • exceptions=on enables exception events in the JVM and immediately starts the exception profiling. This is the default mode on Oracle JDK/OpenJDK HotSpot (i.e. non-IBM JVMs).
  • exceptions=off enables exception events in the JVM but does not immediately starts the exception profiling that can instead be started later in runtime.
  • exceptions=disable fully disables exception events in the JVM to totally eliminate corresponding overhead. This is the default mode on IBM JVMs because the overhead is significant.

When you are connected to the profiled application, use corresponding toolbar button to start/stop the profiling.


The following actions are available in the popup menu:

  • Lines can be copied by using File | Copy (Ctrl+C).
  • File | Export to... (Ctrl+S) - exports view to different formats.
  • Tools | Open in IDE (F7) - opens method declaration in IDE editor. See IDE integration.

YourKit uses cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By browsing our website, you consent to our use of cookies and other tracking technologies in accordance with the Privacy Policy.