Upload
455

Subscription preferences

Loading...

Loading icon Loading...

Working...

Zariga Tongy

JVM Architecture Specification Basic The Method Area explained. Part1

10,722 views 11 months ago
JVM Architecture Specification, The Method Area explained. Part1
From Oracle
The Java Virtual Machine(JVM) has a heap that is shared among all Java Virtual Machine threads. The heap is the run-time data area from which memory for all class instances and arrays is allocated.

The heap is created on virtual machine start-up. Heap storage for objects is reclaimed by an automatic storage management system (known as a garbage collector); objects are never explicitly deallocated. The Java Virtual Machine assumes no particular type of automatic storage management system, and the storage management technique may be chosen according to the implementor's system requirements. The heap may be of a fixed size or may be expanded as required by the computation and may be contracted if a larger heap becomes unnecessary. The memory for the heap does not need to be contiguous.

A Java Virtual Machine implementation may provide the programmer or the user control over the initial size of the heap, as well as, if the heap can be dynamically expanded or contracted, control over the maximum and minimum heap size.

The following exceptional condition is associated with the heap:

If a computation requires more heap than can be made available by the automatic storage management system, the Java Virtual Machine throws an OutOfMemoryError.

qa.zariga.com
JVM spécification d'architecture de base La zone Méthode expliqué. part1
JVM体系结构规范基本方法区。第一部分
JVM Architecture Specification Basic Die Methode Gebiet erklärt. Teil1
Read more
JVM Architecture Specification, The Method Area explained. Part1
From Oracle
The Java Virtual Machine(JVM) has a heap that is shared among all Java Virtual Machine threads. The heap is the run-time data area from which memory for all class instances and arrays is allocated.

The heap is created on virtual machine start-up. Heap storage for objects is reclaimed by an automatic storage management system (known as a garbage collector); objects are never explicitly deallocated. The Java Virtual Machine assumes no particular type of automatic storage management system, and the storage management technique may be chosen according to the implementor's system requirements. The heap may be of a fixed size or may be expanded as required by the computation and may be contracted if a larger heap becomes unnecessary. The memory for the heap does not need to be contiguous.

A Java Virtual Machine implementation may provide the programmer or the user control over the initial size of the heap, as well as, if the heap can be dynamically expanded or contracted, control over the maximum and minimum heap size.

The following exceptional condition is associated with the heap:

If a computation requires more heap than can be made available by the automatic storage management system, the Java Virtual Machine throws an OutOfMemoryError.

qa.zariga.com
JVM spécification d'architecture de base La zone Méthode expliqué. part1
JVM体系结构规范基本方法区。第一部分
JVM Architecture Specification Basic Die Methode Gebiet erklärt. Teil1 Show less
Loading...
Working...
Sign in to add this to Watch Later

Add to