Memory leaks don’t have to be hard/scary/tedious problem to solve if we can follow below mentioned 3 simple steps:
Step 1: Capture baseline heap dump
You need to capture heap dump when it’s in the healthy state. Start your application. Let it take real traffic for 10 minutes. At this point, capture heap dump. Heap Dump is basically the snapshot of your memory. It contains all objects that are residing in the memory, values stored in those objects, inbound & outbound references of those object. You can capture Heap dump using the following command:
jmap-dump:format=b,file=<file-path><pid> where pid: is the Java Process Id, whose heap dump should be captured file-path: is the file path where heap dump will be written in to.
If you don’t want to use jmap for capturing heap dumps, here are several other options to capture heap dumps
It’s always better to capture heap dump in the production environment (unless in the test environment, you can mirror the exact production traffic pattern). Traffic type and its volume play a primary role in the type and number of objects created in the memory.
Step 2: Capture troubled heap dump
After doing step #1, let the application run. Before application crashes, take another heap dump once again. Often times, it might be challenging to capture heap dumps before it crashes because we don’t know when the application will crash. Is it after 30 minutes, 3 hours, 3 days? Thus, it’s ideal to start your application with following JVM property:
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<file-path> file-path: is the file path where heap dump will be written in to.
This property will trigger heap dump right when the application experiences OutOfMemoryError.
Step 3: Compare heap dumps
Objects which are causing memory leaks grow over the period. If you can the identify objects whose size has grown between the heap dumps captured in step #1 and step #2, then those are the objects which are causing memory leak.
You can consider using heap dump analyzer tool such as HeapHero.io for this purpose. When you load the heap dumps into HeapHero, it provides rich information about your application’s memory. There is a “Large Objects” section (shown in Fig 1), which reports largest objects that are sitting in the memory. Compare this section between heap dumps captured in step #1 and step #2. If you notice any abnormal growth of objects, then they are the ones which are causing memory leak in your application. You can also click on any of the largest objects to see the children, grandchildren, great-grandchildren objects present in it.Screen shot of this section is shown in Fig #2.