YourKit Early Access Program (EAP) is the easiest way to get in touch with the latest technologies from YourKit.
You can have early access to new products and internal builds.
NOTE: THIS IS PREVIEW SOFTWARE AIMED AT PROVIDING YOU WITH AN OPPORTUNITY
TO TEST THE NEWEST FEATURES SCHEDULED FOR THE NEXT MAJOR RELEASE.
YOURKIT DOES NOT GUARANTEE THAT THIS SOFTWARE WILL RUN TROUBLE-FREE.
USING THIS SOFTWARE IS AT YOUR OWN DISCRETION AND DOES NOT ENTITLE YOU TO ANY
Your comments, suggestions and bug reports are welcome. In the forum you
can discuss product features with YourKit developers and post bug reports.
Download YourKit Java Profiler 2015.12 EAP (*), build 8 (November 16, 2015)
Version 2015.12 (* - the name is subject to change) will be the next release of YourKit Java Profiler.
See change list.
||Windows (x86, x64)
Download and run installer
||Mac OS X (Intel)
Download and unpack zipped application
(x86, x64, ARMv5, ARMv7, AArch64, ppc, ppc64, ppc64le)
Download tar.bz2 archive
tar xfj <archive name>.tar.bz2
||Solaris (SPARC, x86, x64)
Download and unpack ZIP archive
||AIX (ppc, ppc64)
||FreeBSD (x86, x64)
Actually, the ZIP archive is all-in-one: it contains files for all supported platforms,
including Windows, Mac OS X, and Linux.
However, to ensure easiest installation and best user experience,
it is strongly recommended to use a dedicated download option for these platforms instead:
Windows bundle provides convenient installer and bundled JRE,
Mac OS X - a Mac-style application,
Linux - bundled Oracle JRE for x64 which is superior to OpenJDK for UI applications.
Changes in build 8
Memory profiling: added handling of
This class introduced in Java 7 allows to associate a computed value with every class.
For Java 7 and Java 8,
the maps are shown referenced from corresponding
java.lang.Class instances via
an instance field reference
In latest Java 9 there is unfortunately no means to identify which particular class each map belongs to,
and we instead show the maps as being GC roots of type "Held by JVM".
This feature works with HPROF format snapshots only.
JVM's JVMTI API used to create the profiler format snapshot files
does not provide enough information to let the feature work.
IDE integration: bug fixed: internal error when action "Tools | Open in IDE (F7)"
was applied in object explorers to a field referencing an instance of
IDE integration: IntelliJ IDEA: bug fixed: action "Tools | Open in IDE (F7)"
might navigate to a wrong anonymous class in some complex cases
IDE integration: NetBeans 8.1 supported
Changes in build 7
Bug fixed: JBoss might not start from within an IDE due to an improper initialization sequence of its custom MBeans.
Until this fix, it was required to specify
as a workaround.
GC telemetry: new "GC Pauses" graph added under the "Basic telemetry" node in the "Performance counters" tab.
Also, "GC Pauses" graph, if corresponding data is available (currently - on Sun/Oracle Java 7 and newer),
replaces a less informative "Time Spent in GC" in "Memory & GC telemetry" in the "Memory" tab.
Note: time spent in GC curve is also available in the CPU usage graph in the "CPU" tab.
Changes in build 6
Probes: built-in probe Databases rewritten to solve different class loading issues affecting,
in particular, some JBoss configurations, as well as the new module system introduced in Java 9 ("Project Jigsaw").
Agent: probes are never applied (instrumentation is not performed) to in-runtime generated lambda proxy classes
for the purpose of micro-optimization,
as well as to avoid bytecode instrumentation issues in some corner cases which might lead to verification errors
Agent: Java 9 support: optimization:
native methods annotated with @HotSpotIntrinsicCandidate are not instrumented by default
(and thus are not visible in CPU tracing or probes should any be applicable),
to avoid profiling overhead and get rid of JVM warnings like
"Method [java.lang.reflect.Array.getLength(Ljava/lang/Object;)I] is annotated with @HotSpotIntrinsicCandidate
but no compiler intrinsic is defined for the method."
To instrument such methods please specify the agent startup option "_with_intrinsic_candidates".
Command line tool: new commands
to control stack telemetry in runtime
Changes in build 5
Agent: stability improvements
Problem solved: the profiler UI might not start with IBM Java
Bug fixed: some main menu actions under "CPU" submenu were incorrectly enabled in contexts where they were not supposed to work,
resulting in internal error dialogs on invocation
Bug fixed: JDK 9 Early Access with Project Jigsaw might crash on start when running with the agent with enabled bytecode instrumentation
Changes in build 4
HPROF snapshot loading optimization
Deobfuscation support: bug fixed: ProGuard log with line numbers failed to load
I/O error during snapshot loading might lead to the internal error dialog instead of a human-readable messages
Changes in build 3
Caveat: legacy, pre-v2015 license keys are no longer accepted.
New, v2015-style license keys are required.
The profiler will suggest you to get a new key from YourKit if you're using an old one.
Alternatively, you can use an evaluation license.
by-name lookup windows (e.g. Ctrl+N) could hang for a long time on entering a pattern matching a big number of items
to reduce the pause on attach that can be observed for some applications (e.g. IntelliJ IDEA),
the built-in probes
TestNG are now by default disabled
Bug fixed: exception in the update checker thread
Internal improvements and clean up
Changes in build 2
memory snapshot loading speed increased and memory footprint reduced
to save memory, native object IDs used in HPROF snapshots are by default
no longer stored in memory after the snapshot loading is completed.
In effect, individual objects are identified in the UI with their arbitrary indices,
exactly like it works for the profiler format
To load the native IDs please specify
<Profiler Installation Directory>/bin/ui.ini
export of a byte array to a binary file now works much faster
Class list and other object-grouping views now open up to 2 times faster
the installer by default offers to install the profiler
to the 64-bit program directory, e.g.
instead of the 32-bit program directory, e.g.
C:\Program Files (x86).