Understanding the JVM Memory Model and Its Runtime Data Areas

The author introduces himself and notes that both the JVM memory model and the Java memory model are frequent interview topics, emphasizing that despite similar names they address different concerns: the JVM memory model relates to the virtual machine's internal storage, while the Java memory model concerns multithreaded concurrency.

The JVM (Java Virtual Machine) is described as a virtual computer with its own hardware architecture, executing bytecode that enables Java programs to run unchanged across platforms after compilation by javac .

The JVM memory model consists of five runtime data areas: the shared heap, the shared method area, and three thread‑private regions—the JVM stack, the native method stack, and the program counter.

Heap (Heap) : The largest memory region, shared among all threads, storing object instances and arrays. It is divided into the young generation (further split into Eden, From Survivor, To Survivor) and the old generation. Its size is controlled by -Xms (initial) and -Xmx (maximum) parameters, with automatic expansion or contraction based on free‑heap thresholds.

Method Area (Method Area / Metaspace) : Historically called the method area, it stores class metadata, the constant pool, static variables, and JIT‑compiled code. Since Java 8 it is renamed Metaspace, but its function remains the same and it is also shared among all threads.

JVM Stack (JVM Stack) : Each thread creates its own stack composed of stack frames. A stack frame holds the method’s local variables, operand stack, dynamic linking information, and return address, managing method invocation and return.

Native Method Stack (Native Stack) : Similar to the JVM stack but dedicated to native (non‑Java) method execution. Implementations may merge it with the JVM stack, as some HotSpot versions do.

Program Counter (PC Register) : A per‑thread register that points to the next bytecode instruction to execute. It enables thread scheduling, branching, loops, exception handling, and thread resumption after context switches.

In summary, the article covers the five JVM runtime data areas—heap, method area, JVM stack, native method stack, and program counter—highlighting their structures, typical configuration options, and importance for developers to understand and troubleshoot JVM‑related performance and correctness issues.