JVM Architecture in Java
The class loader, the runtime data areas and the execution engine, and how a class file becomes running machine code.
JVM architecture, class loading, heap and stack, garbage collection and JIT.
5 notes
The class loader, the runtime data areas and the execution engine, and how a class file becomes running machine code.
Classes are found, verified, prepared and initialised on first use, by a hierarchy of loaders that delegate upwards.
Where each piece of data actually lives, and what runs out when each area is exhausted.
The collector reclaims objects that can no longer be reached. Understanding reachability explains both leaks and pauses.
Java can still leak: any object the program keeps reachable but no longer needs. Here is how to find and fix them.