Changes in YourKit Java Profiler 2016.02 builds
java.lang.ClassCastException in the built-in probe
Minor improvements and bug fixes
Enter license dialog: added support of HTTP proxies that require the user/password authentication
Database probes: bug fixes
Windows: launcher: bug fixed: the profiler UI might not start if was installed to a directory with non-ASCII characters in its name
IDE integration: NetBeans 8.2 supported
IDE integration: IntelliJ IDEA 2016.3 supported
Agent: bug fixed: when running CPU tracing in attached mode, event stack traces might miss method calls
Agent: startup option
disableall now implies
Bug fixed: the profiler UI might immediately disconnect after successfully connecting to a remote profiling application
Windows: the profiler agent library
yjpagent.dll is digitally signed.
Memory profiling: object explorer: bug fixed:
java.lang.Class instances without children nodes were shown with the expand icon that disappeared on click
Remote profiling: bug fixed: the profiler might not always detect situations
when the profiled application restarted and continued to listen on the same agent port,
erroneously treating the profiling results coming from the new instance as belonging to the old instance.
As the result, different sorts of data inconsistencies might arise.
Remote profiling: terminated remote applications are detected faster,
the UI indicates the disconnected state more promptly
Bug fixed: temporary floating license unlocking issues
IDE integration: NetBeans: bug fixed: "Profile" action might not work for web applications in NetBeans 8.1
IDE integration: IntelliJ IDEA 2016.2 supported
IDE integration: Eclipse: Bndtools run configurations supported
Minor bug fixes
Bug fixed: on Windows, built-in probe Processes could cause a loader leak if the profiled application
launched an external process from a thread with certain context loader
Bug fixed: built-in probe Databases could lead to logged exceptions in Connection.close()
Java 9 support: bug fixed: since JDK 9 build 114, tracing could lead to a stack overflow
IDE integration: IntelliJ IDEA plugin: internal improvements
Agent: bug fixed: bytecode instrumentation of classes with very long methods might lead to VerifyError under certain circumstances
"Java EE statistics" view: prepare call filtering improved for Cassandra database
Built-in probes: minor performance improvement
Other minor internal optimizations and code cleanup
Mac OS X: bug fixed: exception on opening the file chooser dialog in Mac native theme
Minor internal improvements
CPU profiling: tracing: optimization:
line numbers are not recorded by default for calls made from the methods automatically generated for a JSP page.
These line numbers are generally useless because they do not correspond to the JSP source lines,
but instead to the automatically generated Java code.
As the result of the change, profiled results for individual calls to
out.write(...) are aggregated,
which simplifies the result interpretation as well as slightly reduces profiling overhead and memory footprint.
To revert back to the old behavior please specify the startup option
Internal changes and refactorings
com.yourkit.api.Controller: minor changes and JavaDoc cleanup
IDE integration: IntelliJ IDEA 2016.1 supported
Agent: bug fixed: bytecode instrumentation of some very long methods might lead to VerifyError under certain circumstances
Agent: long method bytecode instrumentation improvement.
Some long methods cannot be instrumented with probe, tracing and allocation callbacks simultaneously
because the resulting bytecode does not fit the Java class format limits.
For example, this may happen with Java code automatically generated for a large JSP page.
Previously, no instrumentation was applied to such classes.
Now the agent tries to instrument them with probes only, thus giving the bytecode a chance to fit the limits,
as well as providing most important profiling information.
collection size is immediately shown and the action
Memory | Contained Objects is available for more classes:
UI: triggers: bug fixed: exception on adding a trigger
Probes: bug fixed: possible
java.lang.ClassCastException in the built-in probe Processes
GC pause telemetry: bug fixed: durations were erroneously shown in microseconds instead of milliseconds
profiler settings UI now take less space itself, thus addressing an issue with IDEA's layout not giving enough space to other components in some contexts,
e.g. for server configurations
DataNucleus probe: improvements
OSGi support improved: more cases are handled automatically thus eliminating the need to manually tweak OSGi settings
to allow loading of the profiler classes.
In particular, the change affects some WebSphere Liberty profile configurations.
Added support of DataNucleus (a JPA implementation)
A fire icon indicating hot spot methods is now also available in CPU profiling live call tree,
as well as in object allocation and garbage call trees
Mac OS X: bug fixed: table header jittering in the bright theme