Changes in YourKit Java Profiler 7.0.12 from 7.0.11

• Problem fixed: classes defined with a call to ClassLoader.defineClass() with name=null were not instrumented (changes in agent)
• Fixes in UI

Changes in YourKit Java Profiler 7.0.11 from 7.0.10

• Monitor view: bug fixed: possible exception switching "Show blocked threads only" option
• Minor fixes

Changes in YourKit Java Profiler 7.0.10 from 7.0.9

• Solved problems profiling on some Linux kernels (changes in agent)

Changes in YourKit Java Profiler 7.0.9 from 7.0.8

• IDE integration: Eclipse 3.4 M4 supported
• Profiling on Java 7 is supported (changes in agent)
• UI: fixes in snapshot comparison view
• Bug fixed in "Lost SWT Controls" inspection
• Fixes in JRockit support (changes in agent)
• Fix in IBM Java support (changes in agent)

Changes in YourKit Java Profiler 7.0.8 from 7.0.7

• Optimization: profiler agent reserves less VM pages on startup
• Wall time methods are now configurable in Java 1.3/1.4 too (changes in UI and agent)
• SQL view: grouping now works for statements with leading spaces too
• Problem fixed: JBoss might not start with profiling if it ran on BEA JRockit JVM
• Minor UI bug fixes

Changes in YourKit Java Profiler 7.0.7 from 7.0.6

• IDE integration: ability to explicitly specify additional agent options from within the profiler plugin UI (field "Additional options" on the "Advanced" tab)
• Bug fixed: possibly incorrect values in back traces and merged callees for some recursive functions
• Bug fixed: incorrect sorting by average time column in SQL profiling results
• Bug fixed: profiler API: Controller.captureSnapshot() incorrectly rejected valid SNAPSHOT_HPROF flag
• Minor bug fixes

Changes in YourKit Java Profiler 7.0.6 from 7.0.5

• Optimization: CPU snapshots load much faster
• Improved profiling of applications which use some byte code instrumentation technics, such as some JBoss and Geronimo configurations. Thanks to this improvement, the workaround that required using 'disablej2ee' option to profile such applications, is no longer needed.
• Bug fixed: connecting to an application with already started CPU profiling might show incomplete results
• Bug fixed: snapshots with CPU tracing results might lack invocation counts under some circumstances
• Bug fixes in J2ME profiling

Changes in YourKit Java Profiler 7.0.5 from 7.0.4

• Bug fixed: memory snapshot captured on profiled application shutdown might be invalid
• Bug fixed: problems launching Eclipse JUnit plugin test configurations with profiler
• Bug fixed: problems profiling on some old Linux configurations
• Bug fixed: incorrect array sizes might be reported for 64-bit Java 5 VMs
• Other bug fixes

Changes in YourKit Java Profiler 7.0.4 from 7.0.3

• Bug fixes

Changes in YourKit Java Profiler 7.0.3 from 7.0.2

• Problem fixed: memory snapshots of an application running with debugger could fail to load
• Method lookup bug fixed

Changes in YourKit Java Profiler 7.0.2 from 7.0

• CPU profiling: it is now configurable for which methods a wall time is measured instead of a CPU time. Read more...
• IDE integration: NetBeans 5.5.x integration issues fixed
• Memory profiling: optimization: less memory is needed for loading HPROF snapshots
• Optimization: profiling data requires 5%-10% less memory
• Profiler API: new method Controller.getStatus() (see JavaDoc)
• Minor bug fixes