Runtime for Javas
The Java runtime is the JVM machinery that loads, verifies, compiles and executes bytecode, including the heap, stacks, metaspace, class loaders, the JIT compiler and garbage collection. It sits in the Concurrency and JVM stage and explains memory errors, startup time and why Java code often speeds up after warming up.
Stage: Concurrency and JVM · Part of the Java roadmap · Last reviewed 19 November 2026
What to learn in Runtime
- Describe the heap, thread stacks and metaspace and what each stores
- Explain how generational garbage collection decides which objects to reclaim
- Trace how a class is loaded, linked and initialised by a class loader
- Read a basic GC log or a heap histogram to spot a memory leak
- Explain what the JIT compiler does and why warm-up affects benchmarks
Runtime interview questions
What is the difference between StackOverflowError and OutOfMemoryError?
StackOverflowError happens when a thread's call stack is exhausted, usually from unbounded recursion. OutOfMemoryError means the JVM cannot allocate memory, most often on the heap, because live objects fill it or because of a leak. The causes and fixes are quite different.
What does the JIT compiler do in the JVM?
The JIT compiler watches which methods run often and compiles their bytecode to optimised native machine code at runtime. It can inline calls and remove dead branches using profile data. This is why Java programs are slower at startup and faster once warmed up.
Where Runtime fits in the Java roadmap
Runtime belongs to the Concurrency and JVM stage (intermediate level), which takes about 32 hours. Under the hood.