Loading...

What are the main memory areas managed by the JVM? | Interview Question | TechyTalkWithDev

Core Java Interview Questions

253 Questions

What are the main memory areas managed by the JVM?

What is Garbage Collection in Java?

How does Garbage Collection actually work in Java (mark and sweep)?

What are the different types of garbage collectors available in the JVM?

What is the difference between Young Generation and Old Generation in the heap?

What is the difference between a Minor GC and a Major (Full) GC?

What makes an object eligible for garbage collection in Java?

What is the difference between strong, weak, soft, and phantom references?

What is a memory leak in Java and how can it happen despite garbage collection?

What is a StackOverflowError and when does it occur?

What is an OutOfMemoryError and what are common causes?

What is the difference between stack memory and heap memory in Java?

What is escape analysis in the JVM?

What is the difference between calling System.gc() and actual garbage collection?

What is the finalize() method and why is it deprecated?

What is Metaspace and how does it differ from the old PermGen?

What is the difference between shallow size and deep/retained size of an object?

What do the -Xms and -Xmx JVM flags control?

Interview questions

Question 172 of 253

Free

What are the main memory areas managed by the JVM?

Memory Management & JVM

Heap (stores all objects, shared across threads, garbage collected), Stack (per-thread, stores method frames and local variables), Method Area/Metaspace (stores class metadata, shared), PC Registers (per-thread instruction pointer), and Native Method Stack (for native code calls).

Intermediate5 min

AccentureCapgeminiCognizantOracleIBMAmazon

#JVM Memory#Heap#Stack

What are the main memory areas managed by the JVM?

Shared vs Per-Thread Areas

Heap and Method Area/Metaspace are shared across the whole JVM process, holding data every thread can reach — which is exactly why objects need synchronization when accessed concurrently. Stack, PC Register, and Native Method Stack are each allocated per-thread, so a thread's local variables and call frames are naturally isolated from every other thread without any extra effort.

Shared: Heap, Method Area · Per-thread: Stack, PC Register, Native Method Stack

Shared: Heap, Method Area · Per-thread: Stack, PC Register, Native Method Stack