Unlocking JVM Secrets: A Visual Guide to Java Memory and Execution

Memory is an essential part of any operating system, and Java relies on the JVM to manage it, which simplifies development but can obscure runtime memory issues.

JVM Overall Structure

The following diagram shows the complete JVM architecture:

Class Loading System

The class loading process is illustrated below:

Loading a class involves three steps:

Loading : The bytecode file is loaded using the parent‑delegation model (Bootstrap, Extension, and Application class loaders).

Linking : Includes verification, preparation (class data structure analysis), and resolution (memory allocation and symbol linking).

Initialization : Executes static field assignments and static blocks.

JVM Runtime Data Areas

The runtime data area diagram details each memory region:

Method Area : Stores loaded class metadata, constants, static variables, and JIT‑compiled code. In JDK 8+, this is replaced by Metaspace, which resides in native memory.

Heap : The largest shared region where all object instances are allocated.

Stack : Each thread has its own stack containing frames with operand stacks, local variables, dynamic links, and return addresses.

Program Counter (PC) Register : Holds the current bytecode line number for each thread; it is thread‑private and the only JVM component that cannot cause an OutOfMemoryError.

Native Method Stack : Stores frames for native (C/C++) method calls.

Execution Engine

The execution engine diagram shows how Java code is run:

Java uses two execution modes:

JIT Compilation : Hot code is compiled into optimized native instructions at runtime.

Interpreter : Less frequently executed code is interpreted directly.

JIT improves performance by optimizing hot paths, while the interpreter handles the rest.

Garbage Collection

During execution, many objects become unreachable and are reclaimed by the garbage collector, a topic that can be explored in depth separately.

Native Interaction (JNI)

The Java Native Interface (JNI) enables Java code to call native libraries and vice‑versa, allowing creation of native methods, updating Java objects, invoking Java methods, and handling exceptions from C/C++ or assembly code.

In summary, understanding the JVM’s memory model, class loading, execution engine, and native integration equips developers to diagnose memory‑related issues and write more efficient Java applications.