Garbage collection overview in Java

Introduction

Garbage collection helps automatically clean up memory that your program no longer uses, so your computer doesn't run out of space.

When your program creates many objects and you want to avoid running out of memory.

When you want to prevent your program from crashing due to memory leaks.

When you want to focus on writing code without manually managing memory.

When your application runs for a long time and needs to free unused memory regularly.

Syntax

Java

No direct syntax to call garbage collection; it runs automatically.
You can suggest it by calling:
System.gc();

Garbage collection runs automatically in Java, so you usually don't need to call it yourself.

Calling System.gc() is only a suggestion to the JVM; it may or may not run immediately.

Examples

This line suggests to the Java Virtual Machine to perform garbage collection.

Java

System.gc();

Objects that are no longer referenced can be cleaned up automatically.

Java

// Create objects
String text = new String("Hello");
// After text is no longer used, garbage collector can free its memory

Sample Program

This program creates a String object, removes its reference, and suggests garbage collection. The output confirms the suggestion.

Java

public class GarbageCollectionDemo {
    public static void main(String[] args) {
        // Create an object
        String message = new String("Hello, world!");
        // Remove reference
        message = null;
        // Suggest garbage collection
        System.gc();
        System.out.println("Garbage collection suggested.");
    }
}

Important Notes

Garbage collection helps prevent memory leaks by freeing unused objects.

You cannot predict exactly when garbage collection will run.

Good programming practice is to remove references to objects you no longer need.

Summary

Garbage collection automatically frees memory of unused objects.

You can suggest garbage collection with System.gc(), but it is not guaranteed to run immediately.

It helps keep your program running smoothly without manual memory management.

Practice

1. What is the main purpose of garbage collection in Java?

easy

A. Increase the size of the heap memory

B. Automatically free memory used by objects no longer needed

C. Manually delete objects from memory

D. Compile Java code into bytecode

Solution

1. Step 1: Recall the purpose of garbage collection and evaluate options

   Garbage collection automatically frees memory used by objects that are no longer referenced in the program. Only "Automatically free memory used by objects no longer needed" matches this definition.

2. Final Answer:

   Automatically free memory used by objects no longer needed -> Option B

3. Quick Check:

   Garbage collection = automatic memory freeing [OK]

Hint: Garbage collection frees unused memory automatically [OK]

Common Mistakes:

• Thinking garbage collection deletes objects manually
• Confusing garbage collection with compiling code
• Believing it increases heap size

2. Which of the following is the correct way to suggest garbage collection in Java?

easy

A. GarbageCollector.run()

B. System.collect()

C. Runtime.gcCollect()

D. System.gc()

Solution

1. Step 1: Recall and verify the method to suggest garbage collection

   Java provides System.gc() to suggest that the JVM runs garbage collection. Only System.gc() is a valid Java method; the others are incorrect or do not exist.

2. Final Answer:

   System.gc() -> Option D

3. Quick Check:

   Suggest GC = System.gc() [OK]

Hint: Use System.gc() to suggest garbage collection [OK]

Common Mistakes:

• Using System.collect() which does not exist
• Confusing Runtime methods with System methods
• Assuming garbage collection runs immediately after calling System.gc()

3. Consider the following Java code snippet:

public class TestGC {
  public static void main(String[] args) {
    String s = new String("hello");
    s = null;
    System.gc();
    System.out.println("Done");
  }
}

What is the expected output when this code runs?

medium

A. Done

B. hello

C. No output, program crashes

D. Done followed by garbage collection logs

Solution

1. Step 1: Trace code execution and determine output

   The string object "hello" is created, then the reference s is set to null, making it eligible for GC. System.gc() suggests collection but does not guarantee immediate action or logs. The only guaranteed output is "Done" from the print statement.

2. Final Answer:

   Done -> Option A

3. Quick Check:

   Print statement output = Done [OK]

Hint: System.gc() does not print anything; only explicit prints show [OK]

Common Mistakes:

• Expecting garbage collection logs to print automatically
• Thinking the string "hello" prints after null assignment
• Assuming program crashes due to null reference

4. Identify the error in the following Java code related to garbage collection:

public class GCExample {
  public static void main(String[] args) {
    Object obj = new Object();
    obj = null;
    System.gc;
  }
}

medium

A. Cannot assign null to an Object

B. Object cannot be garbage collected

C. Missing parentheses in System.gc call

D. System.gc is not a valid method

Solution

1. Step 1: Locate the syntax error in the code

   System.gc is a method call requiring parentheses (System.gc()); the code has System.gc without them, causing a compilation error. Assigning null to Object and the method's existence are valid.

2. Final Answer:

   Missing parentheses in System.gc call -> Option C

3. Quick Check:

   Method calls need parentheses [OK]

Hint: Always use parentheses when calling methods like System.gc() [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Thinking null assignment is invalid
• Believing System.gc is not a method

5. You have a Java program that creates many temporary objects inside a loop. Which approach best helps ensure efficient memory use with garbage collection?

hard

A. Set object references to null when no longer needed inside the loop

B. Call System.gc() inside every loop iteration

C. Increase heap size to avoid garbage collection

D. Avoid creating any objects inside the loop

Solution

1. Step 1: Identify best practice for efficient memory use in loops

   Many temporary objects in a loop can pressure memory; explicitly setting references to null when no longer needed helps the GC identify and free them sooner. Frequent System.gc() is inefficient and not guaranteed; larger heap delays issues; avoiding all objects may not be feasible.

2. Final Answer:

   Set object references to null when no longer needed inside the loop -> Option A

3. Quick Check:

   Null references help GC free memory efficiently [OK]

Hint: Nullify unused references to help garbage collection [OK]

Common Mistakes:

• Calling System.gc() too often expecting instant cleanup
• Thinking increasing heap size solves memory leaks
• Believing you must avoid all object creation in loops