YourKit Profiler full changelog

Feature: Eclipse 2026-03 is supported.
Improvement: The OpenSSL library used by the YourKit agent has been updated to version 3.5.5.
Improvement: Bundled runtime and libraries have been updated.

Feature:
Eclipse 2025-12 is supported.
IntelliJ IDEA 2025.3 is supported.
NetBeans 28 is supported.
Improvement:
Bundled runtime and libraries have been updated.

Feature:
IntelliJ IDEA 2025.2 is supported.
Improvement:
Bundled Java runtime has been updated.

Fixed an issue where the profiler might crash on startup on under certain conditions.

Fixed an issue on Linux and macOS where the profiler did not respect the settings in the ~/.yjp/ui.ini file under certain circumstances.

Fixed an issue on Linux and macOS where the profiler did not respect the settings in the ~/.yjp/ui.ini file under certain circumstances.

JVM support:
Feature Java 24 is supported.
Alpine Linux support:
Caveat Minimal supported version of musl C standard library is now 1.2.4.
Networking:
Feature The profiler can now use the AWS CLI to connect to a remote AWS instance and profile your remote Java app by specifying the AWS instance ID.
Profiling via AWS SSM
Improvement When profiling a remote application over SSH, the profiler now detects if SSH port forwarding is disabled on the remote server or if the user has no home directory. This helps identify configuration issues early and prevents confusion when the user cannot attach the profiler to their application.
User interface:
Improvement Navigation drawers now use space more efficiently and do not take up more horizontal space than necessary.
Improvement Capturing a snapshot no longer stops profiling. To stop profiling, use the Stop profiling action in the toolbar.
Improvement Horizontal toolbars in Telemetry charts and Thread states were replaced with vertical ones to save vertical space.
CPU profiling:
Fix Fixed a deadlock that could occur in the OpenJ9 JVM when using virtual threads.
Thread profiling:
Feature Since deadlock analysis is part of thread profiling, we have moved the Deadlocks tab inside the Threads tab. Deadlocks is now a tool within Threads. This change simplifies UI and improves user experience.
Feature The profiler agent now stores Java-level deadlock information in snapshots, enabling post-mortem analysis. In previous versions, deadlocks were only available in live profiling sessions.
Feature The profiler now displays the time spent in a deadlock for deadlocked threads.
Time spent in lock:
Feature An option Focus on selected thread Focus on selected thread has been added. It allows you to estimate CPU usage of only the selected thread.
CPU estimation for selected thread
Feature A new Frozen threads view has been added to the Threads tab. The profiler identifies threads that do not change their stacks or consume CPU time and reports

JVM support
Alpine Linux support
macOS support
Networking
User interface
CPU profiling
Thread profiling
Memory profiling
Object allocation profiling
Exception profiling
Monitor profiling
Telemetry
IDE integration
EE server support
Triggers