When the Java byte code is loaded in JVM, the JVM divides the memory in the following sections
1.Heap
2.Stack
3.Code
4.Static
How the same take place in DVM? Please guide me to understand this.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When the Java byte code is loaded in JVM, the JVM divides the memory in the following sections
1.Heap
2.Stack
3.Code
4.Static
How the same take place in DVM? Please guide me to understand this.
As far as I known, the DVM manages memory the same way as the JVM. Obviously, there will be some differences in the fine details, but if you understand one you should be able to understand the other.
However, your understanding is a little wrong … with respect to the JVM. For HotSpot JVMs (at least), both code and statics (class frames) are allocated within the Heap. I understand that the permgen heap is used but that is heap space, and the space will be garbage collected under certain circumstances.