1 8 java virtual machine

), object references (reference types, which are not equivalent to the object itself and are implemented according to different virtual machines). It may be a reference pointer to the start address of the object, or it may point to a handle representing the object or other location associated with the object, and the ReturnAddress type (the address of a bytecode directive).The 64-bit length of long and double data takes up 2 local variable space (slot

time of garbage collection will continue to increase correspondingly, the corresponding application pause time will also increase correspondingly . Some applications that require a high amount of time, such as a maximum pause time of hundreds of milliseconds, are likely to exceed this limit when the heap space is larger than a few grams, in which case garbage collection becomes a bottleneck for the system to run. To resolve this contradiction, there is a concurrent garbage collection algorithm

StackOverflowError exception will be thrown; when the Virtual Machine stack is dynamically expanded, an OutOfMemoryError will be thrown if you cannot apply for sufficient memory. 　2.3 Native Method Stack) The local method stack and the virtual machine stack play a very similar role. The difference between them is that

Notes 1. Compile Order: Compiler virtual Machine virtual machine Java source file *.java-------> Bytecode *.class------> class Loader--- gt; execution engine A. class file can contain

into: integer bytes, short, Int, long; char, float, and double. The data types in Java have the same scope on any host.There is also a returnvalue type of the original data type that cannot be used in the Java language in the Java Virtual Machine ). This type is used to imp

garbage collection, first understand the internal architecture of the Java Virtual machine, as shown in The middle dashed box part is the run Time data region, which consists of 5 parts, namely the method area, heap, stack, program counter and local method stack. 1. Program counter For a running

Java Virtual Machine (1) Automatic Memory Management MechanismJava memory overflow exceptionI. Summary We can learn with the following questions:Automatic Memory Management Mechanism, As shown below:What operations may cause memory overflow? What types of memory overflow are there? Which areas of memory are full? What

is limited. The sum of the Java heap and direct memory is still limited by the maximum memory given by the operating system"5" garbage collection system---an important part of the >java virtual machine.---> Recycle garbage space on the method area, Java heap, direct memory.

" memory. If the program executes a Java method, the program counter records the bytecode address of the current thread; if the program executes a local method, the program counter is blank (undefined ). Java programmers often say "stack" and "stack". The "stack" refers to the Java Virtual

execution.Load:The load phase is a phase in the class loading mechanism, which is often referred to as "loading," and is mainly done by:1. Obtain a binary byte stream that defines this class by "full name of Class"2. Convert the static storage structure represented by the byte stream to the run-time data structure of the method area3. Generate a Java.lang.Class object representing this class in the Java he

Stackoverflowerror and OutOfMemoryError like the virtual machine stackThe fourth one is the Java heap:Created when the virtual machine is started, with the sole purpose of storing the object instance. Almost all of the object instances are allocated memory here. The

in the JDK1.8 is completely removed, instead of the metadata area, the metadata area is a heap of memory, unlike the persistence zone, if the metadata area size is not specified, the virtual opportunity consumes the system memory until it runs out.1.7. Local Method StackThe local method stack is very similar to the Java stack, and the biggest difference is that the Jav