JVM, Memory & Garbage Collection Interview Questions

JVM architecture consists of ClassLoader, Runtime Data Areas, Execution Engine, Garbage Collector, and Native Method Interface.

JVM memory areas include Heap, Stack, Method Area, Program Counter Register, and Native Method Stack.

Heap memory stores objects and instance variables and is managed by the Garbage Collector.

Stack memory stores method calls, local variables, and references specific to each thread.

Heap stores objects and is shared among threads, while Stack stores method-specific data and is private to each thread.

Garbage Collection is the automatic process of reclaiming memory occupied by unreachable objects.

The Garbage Collector identifies unreachable objects and frees their memory automatically.

Common GC algorithms include Serial GC, Parallel GC, CMS, G1 GC, ZGC, and Shenandoah GC.

OutOfMemoryError occurs when the JVM cannot allocate sufficient memory for new objects.

A memory leak occurs when objects are no longer needed but remain referenced, preventing garbage collection.

Metaspace is the memory area that stores class metadata and replaced PermGen starting from Java 8.

A ClassLoader loads Java classes into memory dynamically during runtime.

Bootstrap ClassLoader, Platform ClassLoader, and Application ClassLoader are the primary ClassLoaders in Java.

The Just-In-Time Compiler converts frequently executed bytecode into native machine code to improve performance.

JVM tuning parameters include heap size settings, garbage collection configurations, thread stack size, and metaspace limits to optimize performance.

Name concrete APIs (collections, concurrency, streams, annotations) tied to JVM, Memory & Garbage Collection. Interviewers want syntax-level clarity plus when you would reach for each feature in production.

Prefer specific checked/unchecked exceptions, wrap lower-level failures with context, and avoid empty catch blocks. For JVM, Memory & Garbage Collection, decide what is recoverable vs fatal to the request thread.

JUnit 5 with Arrange-Act-Assert, Mockito for collaborators, and parameterized tests for edge cases. Keep JVM, Memory & Garbage Collection logic pure where possible so tests stay fast.

Incorrect equals/hashCode break HashMap/HashSet behavior. If JVM, Memory & Garbage Collection stores objects in collections, explain the contract and mutability pitfalls.

Retain only needed references, prefer streaming for large datasets, and avoid accidental caches. Relate leaks or GC pressure to a concrete JVM, Memory & Garbage Collection scenario.