Backend interview prep

Start

JVM GC Logs Interview Questions and Answers

Master Java Garbage Collection log analysis with production-focused interview questions, real GC log examples, JVM logging options, troubleshooting techniques, and best practices.

Introduction

Garbage Collection (GC) logs provide a detailed record of the JVM's memory management activities. They are one of the most valuable tools for diagnosing performance issues, memory leaks, long application pauses, and OutOfMemoryErrors.

In production environments, enabling GC logging allows developers to understand:

  • How frequently garbage collection occurs
  • How much memory is reclaimed
  • How long applications pause
  • Whether Full GC is happening too often
  • If heap sizing is appropriate
  • Whether a memory leak exists

For senior Java developers and architects, the ability to analyze GC logs is considered an essential production troubleshooting skill.

1. What are GC Logs?

Answer

GC Logs are detailed records generated by the JVM whenever Garbage Collection occurs.

They capture information such as:

  • Type of GC
  • Heap usage before GC
  • Heap usage after GC
  • Heap size
  • Pause duration
  • GC cause
  • Collector used

GC logs help identify memory-related performance issues without modifying application code.

2. Why are GC Logs important?

Answer

GC logs provide visibility into JVM memory behavior.

Without GC logs, developers are often forced to guess the reason behind:

  • High CPU usage
  • Long response times
  • Memory leaks
  • Frequent Full GC
  • OutOfMemoryError

GC logs provide factual evidence that helps identify the root cause.

Benefits

  • Detect memory leaks
  • Monitor heap usage
  • Measure GC pause time
  • Identify Full GC frequency
  • Improve JVM tuning
  • Reduce application latency

3. How do you enable GC Logs?

Answer

Java 9 and above

-Xlog:gc*

To write logs into a file:

-Xlog:gc*:gc.log

Java 8

-XX:+PrintGCDetails
-XX:+PrintGCDateStamps
-Xloggc:gc.log

For production systems, logging to a file is recommended because console logs may be lost after application restarts.

4. What information does a GC log contain?

Answer

A typical GC log contains:

  • Timestamp
  • GC type
  • Heap before collection
  • Heap after collection
  • Total heap size
  • Pause duration
  • GC cause
  • Memory regions

Example:

Pause Young (Normal)
250M->80M(1024M)
18ms

Meaning:

  • Heap before GC = 250 MB
  • Heap after GC = 80 MB
  • Total Heap = 1024 MB
  • Pause Time = 18 milliseconds

This information helps determine whether memory is being reclaimed efficiently.

5. How do you read a Young GC log?

Answer

Example:

[2.345s][info][gc]
GC(5) Pause Young (Normal)
512M->120M(2048M)
22ms

Explanation

GC(5)

This is the fifth garbage collection event.

Pause Young

Only the Young Generation was collected.

512M

Heap usage before GC.

120M

Heap usage after GC.

2048M

Total heap size.

22ms

Application was paused for 22 milliseconds.

Young GC is normal and usually occurs frequently.

6. How do you identify Full GC from logs?

Answer

Example:

GC(12)
Pause Full
1800M->950M(2048M)
950ms

This indicates:

  • Entire heap was scanned.
  • Old Generation was cleaned.
  • Application stopped for 950 milliseconds.

Full GC is significantly slower than Young GC because the JVM scans the entire heap.

Frequent Full GC is usually a sign of an underlying memory problem.

7. What are the common GC events found in logs?

Answer

Common events include:

Young GC

Cleans only the Young Generation.

Occurs frequently.

Very fast.

Mixed GC

Occurs in G1GC.

Collects:

  • Young Generation
  • Selected Old Regions

Helps prevent expensive Full GC.

Full GC

Collects the entire heap.

Longest pause.

Should occur rarely.

Concurrent Marking

Runs in the background.

Identifies live objects without stopping application threads for long periods.

8. How can GC logs help detect memory leaks?

Answer

Memory leaks are visible when heap usage continuously increases after every GC.

Example:

Before GC : 700 MB

After GC : 650 MB

Next GC

Before : 900 MB

After : 870 MB

Next GC

Before : 1200 MB

After : 1180 MB

Notice that very little memory is reclaimed.

Eventually:

  • Heap becomes full
  • Full GC becomes frequent
  • OutOfMemoryError occurs

This pattern strongly suggests that objects are remaining reachable and are not being released.

A Heap Dump should be captured to identify the leaking objects.

9. Which tools can analyze GC Logs?

Answer

Several tools simplify GC log analysis.

Popular choices include:

  • GCViewer
  • GCeasy
  • Java Mission Control (JMC)
  • Eclipse Memory Analyzer (MAT) for heap dumps
  • Grafana dashboards using JVM metrics
  • Prometheus with Micrometer

These tools generate visual reports showing:

  • Pause time
  • Heap growth
  • GC frequency
  • Throughput
  • Allocation rate

Visual analysis is much easier than reading thousands of log lines manually.

10. What problems can GC logs reveal?

Answer

GC logs can identify several production issues.

Frequent Young GC

Usually indicates:

  • Small heap
  • Excessive object creation

Frequent Full GC

Possible causes:

  • Memory leak
  • Small Old Generation
  • Large cache
  • High promotion rate

Long Pause Times

Possible causes:

  • Very large heap
  • Full GC
  • Poor GC configuration

Low Memory Recovery

Possible causes:

  • Memory leak
  • Static references
  • Cached objects not removed

GC logs often provide the first clue about these issues.

11. Explain a real production GC log analysis scenario.

Answer

Scenario

A Spring Boot microservice started showing:

  • High response times
  • CPU utilization above 90%
  • Kubernetes pod restarts

GC logs showed:

Young GC every second

Full GC every 2 minutes

Pause Full

2.4 seconds

Investigation

Heap usage kept increasing after every Full GC.

A Heap Dump revealed:

  • Millions of objects stored inside a static cache.
  • Cache entries were never evicted.

Solution

  • Fixed cache eviction policy.
  • Increased heap size.
  • Tuned G1GC.
  • Enabled continuous GC monitoring.

Result

  • Full GC disappeared.
  • Average response time improved from 2 seconds to 180 milliseconds.
  • CPU usage dropped below 45%.

12. What are the best practices for GC logging?

Answer

Follow these production recommendations:

  • Always enable GC logging in production.
  • Store logs in rotating files.
  • Monitor pause times continuously.
  • Analyze trends instead of isolated events.
  • Keep historical GC logs for troubleshooting.
  • Combine GC logs with Heap Dumps when investigating memory leaks.
  • Use dashboards to monitor JVM metrics.
  • Review GC logs after every major release.

GC logging has minimal overhead but provides invaluable diagnostic information.

13. What interview questions are commonly asked about GC logs?

Answer

Interviewers often ask:

  • How do you enable GC logs?
  • How do you identify Full GC?
  • What information is available in a GC log?
  • How do you detect a memory leak using GC logs?
  • How do you investigate long GC pauses?
  • Which tools do you use for GC log analysis?
  • How do you troubleshoot frequent Full GC?
  • How do GC logs help improve application performance?

Being able to explain a real production incident using GC logs demonstrates strong practical experience.

14. What is your step-by-step approach to analyzing GC logs?

Answer

A systematic approach is recommended.

Step 1

Enable GC logging.

Step 2

Collect logs during normal and peak traffic.

Step 3

Measure:

  • Young GC frequency
  • Full GC frequency
  • Pause times

Step 4

Check heap occupancy before and after GC.

Step 5

Look for continuously increasing heap usage.

Step 6

Capture a Heap Dump if memory is not reclaimed.

Step 7

Analyze the Heap Dump using Eclipse MAT.

Step 8

Tune the JVM only after identifying the root cause.

This approach avoids unnecessary JVM configuration changes and focuses on evidence-based troubleshooting.

15. What are the key takeaways about GC Logs?

Answer

GC logs are one of the most powerful diagnostic tools available for JVM applications.

Remember these points

  • Always enable GC logging in production.
  • Young GC is normal and expected.
  • Frequent Full GC requires investigation.
  • Long GC pauses increase application latency.
  • GC logs help identify memory leaks and heap sizing issues.
  • Analyze trends rather than isolated log entries.
  • Combine GC logs with Heap Dumps for complete root-cause analysis.
  • Validate every tuning change using production metrics and load testing.

Mastering GC log analysis allows developers to solve real-world JVM performance issues confidently and is a highly valued skill in senior Java interviews.