Release Notes
VisualVM 2.0.7 has been released on April 20th, 2021. This document describes changes introduced by this release.
System Requirements
Supported OS:
- Microsoft Windows
- Linux: Intel platform, ARM HFLT, AArch64
- macOS: Intel platform, Apple M1
Required Software:
- Oracle JDK 8~16
- OpenJDK 8~16
- GraalVM 19~21
Changes
Features and Enhancements:
- GH-260: Full support for running on JDK 16 and monitoring/profiling Java 16 processes
- GH-262: Add support for Apple M1
- GH-270: Import of plugins from previous VisualVM version
- GH-275: Add information about enabled modules
- GH-279: Add partial progress for retained sizes computation
- GH-254: Branding of updater splash
- Stack trace for Python
- HeapViewer - logical value added Instant, Attributes$Name, FDBigInteger, java.lang.module
- HeapViewer - logical value for java.util classes - collections now display number of elements
- Application recognizer for Gradle
- Application recognizers for JDK tools updated
API Changes:
- GH-282: Add generics to public API of org.graalvm.visualvm.lib.jfluid.heap package
- GH-283: Add a way to obtain Heap from Instance
Fixed Bugs:
- GH-127: Incorrect max heap for G1GC
- GH-257: "Opening snapshot failed." due to incomplete compressed data read
- GH-263: Retained size calculated as negative
- GH-268: Detect that VisualVM is running on Eclipse OpenJ9
- GH-272: References are computed without progressbar
- GH-273: NPE: Cannot invoke "java.lang.management.MemoryMXBean.gc()"
- GH-274: Logical value: '...' added to complete string
- GH-276: Missing known blocking method
- GH-277: Incorrect horizontal scrolling
- GH-278: NPE at LongBuffer.startReading()
- GH-280: Incorrect selection background color on macOS
- HeapViewer - logical value fixed for PythonModule, SourceImpl$Key, InetSocketAddress, BigDecimal
- Memory sampler - improved refreshing under heavy load
- Improved detection of IntelliJ applications
Known Problems
To view all known problems please see the VisualVM Issues page.
To resolve the most common problems please follow the Troubleshooting Guide.