Garbage collection in Java is the JVM’s automatic memory management process. It finds objects your program is no longer using and reclaims their memory so the heap does not fill up.

Quick Scoop

In plain terms, Java garbage collection helps you avoid manually freeing memory the way you might in lower-level languages. When an object no longer has any reachable references, it becomes eligible for collection, and the JVM can remove it later.

How it works

  • Java stores objects on the heap.
  • The garbage collector checks which objects are still reachable from active references.
  • It reclaims memory used by unreachable objects.
  • Some collectors also compact memory to reduce fragmentation.

Why it matters

Garbage collection reduces the risk of memory leaks and saves developers from manually deallocating objects. If the heap keeps growing without reclaiming unused objects, the application can eventually hit an OutOfMemoryError.

Simple example

If you create an object inside a method and nothing outside that method keeps a reference to it, that object usually becomes eligible for garbage collection after the method finishes. The JVM may reclaim it later, not necessarily immediately.

Key idea

Java garbage collection does not mean “objects are deleted instantly.” It means the JVM automatically decides when unused memory can be reused.

If you want, I can also explain minor vs major GC or show a code example.