An Oracle blog about NetBeans Profiler

VisualVM 1.3.9 Released

VisualVM 1.3.9 has been released. The original home at java.net is going dark next year, so the project has been migrated to GitHub, including the sources, downloads and update centers. The web content will be incrementally transferred from the original pages to the new address over the next weeks.

VisualVM 1.3.9 introduces experimental support for both running on JDK 9 and monitoring Java 9 processes. The tool has been tested to work with Oracle JDK 9 build 138. Future builds of the JDK may introduce incompatible changes which will prevent VisualVM from running on/monitoring it.

The other changes include enabling support for analyzing VM coredumps on Microsoft Windows, improving the --openid and --openpid parameters to open the process on a defined tab (visualvm --openpid 12345@2 will open a process with PID 12345 in VisualVM with the Monitor tab preselected) and remembering decisions about future host/JMX connection resolving on startup.

Many bugs have been fixed and the tool is built on the NetBeans Platform 8.0.2.

Related links: New VisualVM Home at GitHub, Download VisualVM, Release Notes, VisualVM Feedback, JDK 9 EA Builds

Join the discussion

Comments ( 4 )
  • guest Friday, January 27, 2017

    Hi. Is there an explanation as to why JVisualVM was removed from JDK9 and introduced as a separate project?

    I saw this bug https://netbeans.org/bugzilla/show_bug.cgi?id=258808, but the exact cause and reasoning are not discussed.

  • Jiri Sedlacek Friday, January 27, 2017

    VisualVM has always been a separate project. Including it into and removing it from JDK is up to the JDK team decision.

    The bug is just one of the problems caused by running on Java 9. VisualVM will eventually provide full support for running on/monitoring Java 9.

  • guest Tuesday, February 21, 2017


    This tool is extremely useful. Having it inside of JDK gave additional guarantee that it would work with a specific version of JDK. I can always ask our customer to run the tool, because in their mind it is part of the JDK. When the tool is separated these advantages dissapear and it becomes just another tool for Java.

  • Jiri Sedlacek Tuesday, February 21, 2017

    VisualVM continues to be part of the JDK 8. Once your customers switch to JDK 9, they can use the bundled Mission Control tool, standalone VisualVM from GitHub or just any other tool for Java.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.