- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Virtual threads support
- Object allocation profiling
- Memory profiling
- Monitor profiling
- Exception profiling
- Telemetry
- Probes: monitor events of various kinds
- Events in user interface
- Event inspections
- Built-in probes
- com.yourkit.probes.builtin.Threads
- Class loading probe
- com.yourkit.probes.builtin.AwtEvents
- Probe classes
- Monitoring method invocation events
- Probe class annotation @MethodPattern
- Callback onEnter()
- Callback onReturn()
- Callback onExit()
- Callbacks onUncaughtException() and onUncaughtExceptionExt()
- Parameter annotation @Param
- Parameter annotation @Params
- Parameter annotation @This
- Parameter annotation @ClassRef
- Parameter annotation @MethodName
- Parameter annotation @MethodTimeMs
- Parameter annotation @MethodTimeNs
- Parameter annotation @MethodParameterTypes
- Parameter annotation @MethodSignature
- Parameter annotation @OnEnterResult
- Parameter annotation @ReturnValue
- Parameter annotation @ThrownException
- Probe application rules
- Data storage
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary
- Filters
- Profiler command line
- Export of profiling results to external formats
- Profiler Java API
- Profiler HTTP API
- Settings
- Troubleshooting and FAQ
com.yourkit.probes.builtin.AwtEvents
Description
This built-in probe records AWT/Swing events longer than 0.3 second, which can cause UI irresponsiveness.
Problem detection: irresponsive UI
If a long operation is performed directly in the event queue thread, UI may become irresponsive: do not redraw, do not accept user input etc.
Good practice is to perform long operations in a separate thread, and use the event queue to present prepared results only.
For analysis of the results provided by this probe, select AWT event in probes table and apply CPU usage estimation.
Source code location
<Profiler Installation Directory>/probes/src