You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To capture a heap dump of, for example, a Ruby application for later analysis, start your application and let it run for a few seconds to warm up.
38
+
To capture a heap dump for later analysis, start your application and let it run for a few seconds to warm up.
29
39
Then right-click its process in VisualVM and invoke the Heap Dump action.
30
-
A new heap viewer for the Ruby process opens.
31
-
32
-
__Note:__ Heap dump support must be explicitly enabled when using [Native Image](../reference-manual/native-image/README.md).
33
-
Add the `--enable-monitoring=heapdump,jvmstat` option when invoking the `native-image` tool to enable the heap dump feature and allow VisualVM to detect native executables via `jvmstat`.
34
-
This way your application will handle signals and capture a heap dump when it receives the `SIGUSR1` signal.
35
-
See the [Generating Native Heap Dumps](../reference-manual/native-image/guides/create-heap-dump-from-native-executable.md) page for details on capturing heap dumps from a native image process.
36
40
37
41
### Analyzing Objects
38
42
Initially the Summary view for the Java heap is displayed.
Stringwarning = String.format("the option '%s' contains value(s) that are not supported on Windows: %s. Those values will be ignored.", getDefaultMonitoringCommandArgument(),
0 commit comments