After collecting the Heap Dump, we would need to parse the Heap Dump file for analysis to produce a readable and easy-to-understand report.ДЄn Analyzer can help to quickly calculate the retained sizes of objects, see who/what is preventing the Garbage Collector from collecting objects and identify memory leak suspects. The Heap Dumps collected are not readable directly. Run below jmap command to generate the Heap dump for given process with PID with given. In the Java bin directory, you can use jmap utility to get a live heap dump and/or dump the heap on OOM with a JVM argument.ДЇind the ProcessId (PID) for the Java application by running ps aux | grep java. On-demand via jmap utility (OracleJDK/OpenJDK HotSpot) If the applcation hits OOM Error frequently and is creating Heap dumps often, the disk space might run out of space soon causing many more cascading issues! It's important to note that the dump file can be huge, up to Gigabytes, so ensure that the target file system has enough space.Note that there will not be any overhead involved unless an OOM actually occurs, so it's recommended to enable this for all production systems which can be handy if and when any memory issue comes. If the Java application is configured the VM flag -XX:+HeapDumpOnOutOfMemoryError, then a heap dump is collected on the first OOM Error.We can collect Heap Dumps for a Java application through: hprof memory snapshots on demand or automatically configure the programs to create Heap dumps, which can help with uncovering inefficient heap usage and debugging memory leaks. Java has a built-in feature for dumping heap snapshots to files in HPROF binary format. Collecting and analysing the Heap Dumps is great way to identify and root cause lot of memory related issues. Java uses the heap as the storage for Java objects.

1 : Java heap space Working with Java Heap Dumps

Jprofiler retained size