VisualVM Profiler

Profiling

Recent change notes

1.0.0 (2008-12-08)
- Support for VisualVM 1.1
- Autodetect Java version when choosing the profiler interface to use (although officially VisualVM supports only Java 6 and 7)

0.4.2 (2008-11-26)
- Fixed possible NPE if the MainClass returned by IDEA was null

0.4.1 (2008-11-24)
- Fixed inconsistent naming of profiler actions (IDEA 8 only)
- Fixed the profiler actions appearing in every file's context menu (IDEA 8 only)

0.4.0 (2008-11-24)
- Compatible with IDEA 8
- Uniquely identify the application launched by IDEA

0.3.0 (2008-11-12)
- Memory profiling
- Settings are copied to VisualVM's user interface
- Saved space in the run configuration dialog by moving help texts to tooltips

0.2.0 (2008-11-09)
- Works with the bundled VisualVM which comes with JDK 6 Update 7 and above
- Detects bundled VisualVMs automatically, in which case no configuration is necessary
- Should work also with Linux and Mac (not tested, also not sure about 64 bit JVMs)
- Defaults to jdk15 profiler interface for better compatibility (hardcoded)
- Warns about invalid configuration

0.1.0 (2008-11-06)
- Initial release
- CPU profiling (Windows Java 6 only)

Known issues
- VisualVM may freeze if the application finishes execution before its window opens up in VisualVM. A workaround is to add Thread.sleep(1000) or a longer delay to the beginning of the main() method of the profiled application.

Future plans
- A button for opening the currently running (non-profiled) program in VisualVM, so that the user will not need to manually select the program from VisualVM's list of all running Java programs
- Integration with NetBeans IDE's profiler if it has benefits over VisualVM (they both use internally the same NetBeans Profiler)