深入java,初探jvm（Deep Java of JVM）.docVIP

深入java,初探jvm（Deep Java of JVM） Your location: Java JVM in-depth development of deep Java, JVM Enter JVM, shallow water can also catch fish! This is not a description of what the JVM article, nor the characteristics of cross platform JVM, nor about JVM security feature articles, but not on the JVM instruction operation, data calculation of the article, this article focuses on the type of life cycle. The type of life cycle involves: class loading, JVM architecture, the garbage collection mechanism. Why do you want to tell the JVM architecture? Because the class loading and garbage collection mechanism are closely related and JVM architecture. What is the JVM architecture? When the JVM is up and running, it will apply to a system memory area (different JVM implementation may be different, some can use virtual memory), the memory will separate the part of the storage of many things, such as: the object created by the program, the return value parameters passed to the method, local variables and so on, we will be the the memory is called runtime data area, runtime data area can be divided into the method area, stack, Java stack, PC register, native method stacks. See the picture above, and you can probably understand the explanation of JVM system is what, but you may not understand the runtime data area inside the method area used to doing. Method: when a class file loading of the virtual machine, it parses the type information from the binary data file contains the class. However, these types of information in the method area. Because the method is all threads sharing area, so we have to consider the thread safe data. If two threads are trying to find the lava class, lava class has not been loaded in the case, there should be only one thread to load, and another thread waiting. Pc register: each new thread will get their PC registers and a Java stack frame. Heap: all objects stored at runtime. The heap is a thread shared memory area, so when we write multi-threaded pr