Get almost unlimited capabilities to analyze issues specific to your particular application, as well as automatically recognize problems typical to wide range of applications.
New feature: UI: ability to ignore particular references in paths. This feature is a great aid when investigating memory leaks, because it immediately shows whether nulling particular reference eliminates the leak, and if not, which remaining references you should also consider.
New feature: UI: Class hierarchy slave view allows to see superclasses and extending classes for given class
New feature: UI: Class list has new slave view "Class statics", which allows to quickly browse static fields and constant pool references of selected class
java.lang.Classinstances) for selected object(s)
java.lang.Threador subclasses) in reference explorers
New feature: "Method list" is available in live view, in addition to "Call tree"
Improvement: it is now possible to specify in the plugin UI whether a 32-bit Java or a 64-bit Java is used to launch profiled application, in order to choose appropriate profiler agent. Previously, it was required to re-run IDE integration wizard to change the JVM kind. Also, it is now possible to choose Java kind per run configuration in IDEs which provide such capabilities (Eclipse, IDEA). See tab "32-bit or 64-bit Java Selection" in the plugin configuration UI.
For example, see how the configuration looks in Eclipse:
... and in NetBeans:
Of course, IDEA and JDeveloper are also supported.
New feature: Welcome screen: "Monitor Local Applications" panel provides the option "Show all running JVMs" to see all Java applications running on the machine, including those not started with the profiler agent. This helps troubleshooting possible connection problems.
New feature: table columns are resizeable, and if column content does not fit, a scroller appears. Also, wide tables are scrollable themselves, like tables in spreadsheet applications.
This dramatically improves usability working with Probes results.
Another view to mention which will greatly benefit from this feature is Threads where very long thread names will not be cut off anymore.
org.apache.*,+org.apache.jsp.*will filter out Tomcat internals, but will not filter classes of particular JSP pages, which Tomcat generates in package
New feature: profiler agent log is written to file
Successfully started agent writes to
stderr only the following line:
With this new approach, the profiler agent log messages are easier to find if profiled application redirects its output to own log files or filters it, and will not be lost if the output goes directly to console, or if there is no console at all if the profiled application runs as a service. Also, the profiled application's output and its own log files are not cluttered with extra messages.
(Since 9.0.3) New feature: periodic snapshot trigger allows to choose the kind of snapshot to capture: performance, memory in *.snapshot format or memory in HPROF format. Previously, the periodic snapshot trigger only captured memory snapshots in *.snapshot format.
In particular, this feature helps to monitor long running applications. By default, telemetry buffer capacity is approximately 1 hour, and older telemetry is not available. Instead of increasing the telemetry buffer capacity with "telemetrylimit" startup option, you can periodically capture performance snapshots to ensure that that oldest telemetry will not be lost.
com.yourkit.api.Controller: added methods
com.yourkit.api.Controller.startCPUProfiling()can be instructed to use current filter and wall time settings stored in user home, by passing 'null' as parameters
bin/yjp.inion all platforms. Previously, it was required to modify different files on different platforms.
yjp.shwith an outdated Java version
yjp.shautomatically starts the profiler UI with a 64-bit JVM if it is available