Java Heap Dump Analysis Interview Questions & Answers

Introduction

When a Java application runs out of memory or continuously consumes more Heap over time, the most valuable diagnostic artifact is a Heap Dump.

A Heap Dump allows engineers to answer questions such as:

• Which objects consume the most memory?
• Why are these objects still alive?
• Is there a memory leak?
• Which objects retain the largest portion of Heap?
• What is causing the OutOfMemoryError?

Heap Dump analysis is one of the most important production support skills for Senior Java Developers, Technical Leads, and Solution Architects.

---

1. What is a Heap Dump?

Answer

A Heap Dump is a snapshot of all objects currently stored in JVM Heap memory.

It contains:

• Object instances
• Class information
• Object references
• Object sizes
• Retained memory
• GC Roots

Illustration

JVM Heap

↓

Customer

↓

Orders

↓

Invoices

↓

Products

↓

Object References

Heap Dumps provide a complete picture of Heap memory at a specific moment.

---

2. When should you capture a Heap Dump?

Answer

Common situations include:

• OutOfMemoryError
• Continuous Heap growth
• Frequent Full GC
• Suspected memory leak
• Kubernetes/OpenShift pod restarts
• High memory alerts
• Production performance degradation

Heap Dumps should be captured before restarting the JVM whenever possible.

---

3. How do you capture a Heap Dump?

Answer

Using jcmd

jcmd <PID> GC.heap_dump heap.hprof

Using jmap

jmap -dump:live,file=heap.hprof <PID>

Automatically on OutOfMemoryError

-XX:+HeapDumpOnOutOfMemoryError

Specify output location

-XX:HeapDumpPath=/logs/heapdump

Automatic Heap Dump generation is recommended for production systems.

---

4. What information does a Heap Dump contain?

Answer

A Heap Dump contains:

• Objects
• Classes
• Object graph
• References
• Retained Heap
• Shallow Heap
• GC Roots
• Arrays
• Collections

This information helps determine why memory is not being reclaimed.

---

5. What is Shallow Heap?

Answer

Shallow Heap is the memory consumed by an object itself.

Example

HashMap Object

↓

64 Bytes

It does not include referenced child objects.

Shallow Heap represents only the object's own footprint.

---

6. What is Retained Heap?

Answer

Retained Heap is the amount of memory that would be freed if an object and all objects reachable only through it were garbage collected.

Example

Cache

↓

Orders

↓

Invoices

↓

Customers

↓

Retained Heap

500 MB

Large retained heaps usually indicate major memory consumers.

---

7. What is a Dominator Tree?

Answer

The Dominator Tree identifies objects responsible for retaining large portions of Heap memory.

Illustration

ApplicationCache

↓

HashMap

↓

Customer Objects

↓

Order Objects

If the root object is removed,

all retained child objects become eligible for Garbage Collection.

The Dominator Tree is one of the most useful MAT views.

---

8. What are GC Roots?

Answer

GC Roots are the starting points used by the Garbage Collector to determine object reachability.

Examples

• Static variables
• Active threads
• JNI references
• Thread stacks
• System classes

Illustration

GC Root

↓

Static Cache

↓

HashMap

↓

Objects

Any object reachable from a GC Root cannot be garbage collected.

---

9. What is the Histogram in Eclipse MAT?

Answer

The Histogram groups objects by class.

Example

HashMap

250,000 Objects

----------------

String

600,000 Objects

----------------

ArrayList

120,000 Objects

It helps identify classes consuming the most Heap memory.

---

10. What is the Leak Suspect Report?

Answer

The Leak Suspect Report is an automatic analysis generated by Eclipse MAT.

It highlights:

• Large retained objects
• Potential memory leaks
• Dominator chains
• GC Root paths
• Suspected leak candidates

This report provides an excellent starting point for investigation.

---

11. Explain a production use case.

Answer

Scenario

A Spring Boot application running on OpenShift restarted every few days because of OutOfMemoryError.

Symptoms

Heap Usage

↓

75%

↓

90%

↓

100%

↓

Pod Restart

Investigation

Heap Dump

↓

Eclipse MAT

↓

Leak Suspect Report

↓

Dominator Tree

↓

Static HashMap

Root Cause

A static cache stored completed customer reports indefinitely.

Solution

• Replaced the static map with Caffeine cache.
• Configured maximum size.
• Added time-based expiration.

Result

• Heap stabilized around 45%.
• Full GC frequency decreased.
• No further pod restarts.
• Application remained stable under production load.

---

12. What are common Heap Dump analysis mistakes?

Answer

Common mistakes include:

Capturing the dump after restarting the JVM.

Ignoring Retained Heap.

Looking only at object count.

Ignoring GC Root paths.

Ignoring Dominator Tree.

Increasing Heap instead of fixing leaks.

Analyzing only one Heap Dump.

Always compare Heap Dumps over time when possible.

---

13. What are the best practices?

Answer

Recommended practices

• Enable automatic Heap Dumps on OutOfMemoryError.
• Analyze with Eclipse MAT.
• Review the Leak Suspect Report first.
• Examine the Dominator Tree.
• Investigate large retained objects.
• Follow GC Root paths.
• Compare multiple Heap Dumps.
• Configure bounded caches.
• Remove unnecessary object references.
• Validate memory improvements after deployment.

---

14. Which tools are commonly used?

Answer

Common Heap analysis tools

Tool	Purpose
Eclipse MAT	Heap Dump analysis
jcmd	Capture Heap Dumps
jmap	Capture Heap Dumps
Java Flight Recorder (JFR)	Allocation profiling
JDK Mission Control (JMC)	JFR analysis
VisualVM	Heap monitoring
YourKit	Commercial Heap analysis
JProfiler	Commercial profiling
Datadog	Memory monitoring
Grafana	Heap dashboards

These tools work together to diagnose memory issues efficiently.

---

15. What interview tips should you remember?

Answer

Interviewers commonly ask:

• Heap Dump
• Shallow Heap
• Retained Heap
• Dominator Tree
• GC Roots
• Histogram
• Leak Suspect Report
• Eclipse MAT
• OutOfMemoryError
• Production scenarios

Remember

• Heap Dumps capture JVM Heap memory.
• Shallow Heap is the object's own memory.
• Retained Heap includes dependent objects.
• The Dominator Tree identifies major memory retainers.
• GC Roots explain object reachability.
• MAT is the industry-standard Heap analysis tool.
• Always analyze before increasing Heap size.
• Support answers with real production troubleshooting examples.

---

Summary

Heap Dump Analysis is one of the most important production troubleshooting skills in Java. By using Heap Dumps together with Eclipse MAT, engineers can identify retained objects, analyze GC Root paths, investigate Dominator Trees, and resolve memory leaks that lead to OutOfMemoryError and production instability. A structured, evidence-based approach ensures accurate diagnosis and long-term application stability.

Key Takeaways

• Understand Heap Dump fundamentals.
• Learn when to capture Heap Dumps.
• Capture Heap Dumps using jcmd or jmap.
• Understand Shallow Heap and Retained Heap.
• Analyze Dominator Trees effectively.
• Learn the role of GC Roots.
• Use Histograms and Leak Suspect Reports.
• Follow enterprise memory troubleshooting practices.
• Use Eclipse MAT for production analysis.
• Support interview answers with real production examples.

---