Oracle Generics and Certification

Invoking Garbage Collection Programmatically – Object Lifetime

•

, , , , ,

•

2 min read

10.4 Invoking Garbage Collection Programmatically

Although Java provides facilities to invoke the garbage collector explicitly, there are no guarantees that it will be run. The program can request that garbage collection be performed, but there is no way to force garbage collection to be activated.

The System.gc() method can be used to request garbage collection.

static void gc()

Requests that garbage collection be run.

Alternatively, corresponding methods in the Runtime class can be used. A Java application has a unique Runtime object that can be used by the application to interact with the JVM. An application can obtain this object by calling the method Runtime.getRuntime(). The Runtime class provides several methods related to memory issues:

static Runtime getRuntime()

Returns the Runtime object associated with the current application.

void gc()

Requests that garbage collection be run. There are no guarantees that it will be run. It is recommended to use the more convenient static method System.gc().

long freeMemory()

Returns the amount of free memory (bytes) in the JVM that is available for new objects.

long totalMemory()

Returns the total amount of memory (bytes) available in the JVM, including both memory occupied by current objects and memory available for new objects.

The following points regarding automatic garbage collection should be noted:

  • Trying to initiate garbage collection programmatically does not guarantee that it will actually be run.
  • Garbage collection might not even be run if the program execution does not warrant it. Thus any memory allocated during program execution might remain allocated after program termination, but will eventually be reclaimed by the operating system.
  • There are also no guarantees about the order in which the objects will be garbage collected. Therefore, the program should not make any assumptions based on this criteria.
  • Garbage collection does not guarantee that there will be enough memory for the program to run. A program can rely on the garbage collector to run when memory gets very low, and it can expect an OutOfMemoryError to be thrown if its memory demands cannot be met.

Leave a Reply

Your email address will not be published. Required fields are marked *

Collections and Generics

  • Invoking Garbage Collection Programmatically – Object Lifetime

    •

    2 min read

    10.4 Invoking Garbage Collection Programmatically Although Java provides facilities to invoke the garbage collector explicitly, there are no guarantees that it will be run. The program can request that garbage collection be performed, but there is no way to force garbage collection to be activated. The System.gc() method can be used to request garbage collection.…

    0

  • Bounded Type Parameters – Generics

    •

    4 min read

    11.6 Bounded Type Parameters In the declaration of the generic class Node<E>, the type parameter E is unbounded— that is, it can be any reference type. However, sometimes it may be necessary to restrict what type the type parameter E can represent. The canonical example is restricting that the type parameter E is Comparable<E> so…

    0

  • Raw Types and Unchecked Warnings – Generics

    •

    7 min read

    Raw Types and Unchecked Warnings A generic type without its formal type parameters is called a raw type. The raw type is the supertype of all parameterized types of the generic type. For example, the raw type Node is the supertype of the parameterized types Node<String>, Node<Integer>, and Node<Node<String>>. The last parameterized type is an…

    0

  • Static Initializer Blocks – Object Lifetime

    •

    2 min read

    10.7 Static Initializer Blocks Java allows static initializer blocks to be defined in a class. Although such blocks can include arbitrary code, they are primarily used for initializing static fields. The code in a static initializer block is executed only once, when the class is loaded and initialized. Local variables in static and instance initializer…

    0

  • Wildcards – Generics

    •

    5 min read

    11.4 Wildcards In this section, we discuss how using wildcards can increase the expressive power of generic types. But first we examine one major difference between array types and parameterized types. The generic class Node<E> used in this subsection is defined in Example 11.2, p. 568. The Subtype Covariance Problem with Parameterized Types The following…

    0

  • Exception Handling in Static Initializer Blocks – Object Lifetime

    •

    3 min read

    Exception Handling in Static Initializer Blocks Exception handling in static initializer blocks is no different from that in static initializer expressions: Uncaught checked exceptions cannot be thrown. Code in initializers cannot throw checked exceptions. A static initializer block cannot be called directly. Therefore, any checked exceptions must be caught and handled in the body of…

    0

  • The Diamond Operator – Generics

    •

    4 min read

    The Diamond Operator (<>) In the object creation expression of the new operator, the actual type parameter was explicitly specified after the class name—in contrast to the constructor declaration. Click here to view code image Node<String> lst = new Node<String>(“Hi”, null); // Explicit actual type parameter The actual type parameters can be omitted, but not…

    0

  • Generic Types and Parameterized Types – Generics

    •

    6 min read

    11.2 Generic Types and Parameterized Types We first introduce the basic terminology and concepts relating to generics in Java. Note that the discussion here on generic and parameterized types also applies to enum types (§5.13, p. 287) and record classes (§5.14, p. 299). Generic Types A generic type is a reference type that defines a…

    0

  • Declaration Order of Initializer Expressions – Object Lifetime

    •

    5 min read

    Declaration Order of Initializer Expressions When an object is created using the new operator, instance initializer expressions are executed in the order in which the instance fields are declared in the class. Java requires that the declaration of a field must occur before its usage in any initializer expression if the field is used on…

    0

  • Lower Bounded Wildcard References: – Generics

    •

    2 min read

    Lower Bounded Wildcard References: <? super Type> Using a reference of type Node<? super Number>, where Type is Number, we can only put a Number or a subtype object of Number into the node, as such a number would also be a subtype object of any supertype of Number. Since we cannot guarantee which specific…

    0