
Thread related data & stacks (very useful for sudden Java heap increase problems, especially when combined with thread dump analysis)Ī heap dump does not contain memory allocation information, therefore you cannot work out what created the objects or where the objects were created.Garbage collection roots or objects that are accessible from outside the heap (System classloader loaded resources such as rt.jar, JNI or native variables, Threads, Java Locals and more…).


So let’s start the discussion with some basics: What is Memory Heap? Such snaps are comparable and help to identify the root cause related to a memory leak.

Heap Dump provides a snap of objects and their status in the memory at a particular time. What about the computer (JVM) world? How will you analysis the status of the objects or any memory leak problem? There must be some kind of snap or data which can help you to solve the purpose of heap memory leak. But this is something which we can see in real life.

Finding the difference in the objects and their condition is bit easy and comparable with a snap. Because you can easily visualize them and identify the differences using your senses. Would you be able to find the difference between them? I assume your answer will be ‘Yes’.
