JVM PermGen – where art thou?
This post covers some basics of JVM memory structure and quickly peeks into PermGen to find out where it has disappeared since advent of Java SE 8.
The JVM is just another process running on your system and the magic begins with the java command. Like any OS process, it needs memory for its run time operations. Remember – the JVM itself is a software abstraction of a hardware on top of which Java programs run and boast of OS independence and WORA (write once run anywhere).
Quick coverage of the JVM memory structure
As per the spec, JVM is divided into 5 virtual memory segments.
- Method (non heap)
- JVM Stack
- Native Stack
- PC Registers
- Every object allocated in your Java program requires to be stored in the memory. The heap is the area where all the instantiated objects get stored. Yes – blame the new operator for filling up your Java heap!
- Shared by all threads
- The JVM throws java.lang.OutOfMemoryError when it’s exhausted
- Use the -Xms and -Xmx JVM options to tune the Heap size
- Eden (Young) – New object or the ones with short life expectancy exist in this area and it is regulated using the -XX:NewSize and -XX:MaxNewSize parameters. GC (garbage collector) minor sweeps this space
- Survivor – The objects which are still being referenced manage to survive garbage collection in the Eden space end up in this area. This is regulated via the -XX:SurvivorRatio JVM option
- Old (Tenured) – This is for objects which survive long garbage collections in both the Eden and Survivor space (due to lingering references of course). A special garbage collector takes care of this space. Object de-alloaction in the tenured space is taken care of by GC major
- Also called the non heap area (in HotSpot JVM implementation)
- It is divided into 2 major sub spaces
Permanent Generation – This area stores class related data from class definitions, structures, methods, field, method (data and code) and constants. Can be regulated using -XX:PermSize and -XX:MaxPermSize. IT can cause java.lang.OutOfMemoryError: PermGen space if it runs out if space.
Code Cache – The cache area is used to store compiled code. The compiled code is nothing but native code (hardware specific) and is taken care of by the JIT (Just In Time) compiler which is specific to the Oracle HotSpot JVM.
- Has a lot to do with methods in the Java classes
- Stores local variables and regulates method invocation, partial result and return values
- Each thread in Java has its own (private) copy of the stack and is not accessible to other threads.
- Tuned using -Xss JVM option
- Used for native methods (non Java code)
- Per thread allocation
- Program counter specific to a particular thread
- Contains addresses for JVM instructions which are being exceuted (undefined in case of native methods)
So, that’s about it for the JVM memory segment basics. Coming to back to the Permanent Generation.
So where is PermGen ???
Essentially, the PermGen has been completely removed and replaced by another memory area known as the Metaspace.
Metaspace – quick facts
- It’s part of the native heap memory
- Can be tuned using -XX:MetaspaceSize and -XX:MaxMetaspaceSize
- Clean up initiation driven by XX:MetaspaceSize option i.e. when the MetaspaceSize is reached.
- java.lang.OutOfMemoryError: Metadata space will be received if the native space is exhausted
- The PermGen related JVM options i.e. -XX:PermSize and -XX:MaxPermSize will be ignored if present
This was obviously just the tip of the iceberg. For comprehensive coverage of the JVM, there is no reference better than the specification itself !
You can also explore
|Reference:||JVM PermGen – where art thou? from our JCG partner Abhishek Gupta at the Object Oriented.. blog.|
It would be better to give link to JVM specification instead of JLS specification as JLS does not specify anything about storage areas.
I’m pretty sure in JVM Java and native stacks are the same memory segment – it’s not separated.