- System requirements
- Profiler architecture
- Profiler installation
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead: how to reduce or avoid
- Solving performance problems
- CPU profiling
- Memory profiling
- Garbage collection
- Exception profiling
- Performance charts
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler API
- Profiler HTTP API
Exceptions in .NET can be performance killers, especially when thrown and caught frequently. YourKit .NET Profiler captures data on exceptions that have been thrown and provides stack traces and other contextual information. This data allows you to identify exception-related bottlenecks, which can be especially useful for debugging or optimizing error-prone areas of your application.
Exceptions tab shows exceptions which were thrown in the profiled application:
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 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, you may want to stop it to minimize profiling overhead.
The profiling is enabled by default, unless the
exceptions=off startup option is specified.
When you are connected to the profiled application, use 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).