Garbage Collection — Explained with Examples

Garbage collection (GC) is automatic memory management where the runtime identifies and reclaims memory that is no longer reachable by the program. Developers are freed from manually allocating and deallocating memory (as required in C/C++ with malloc/free).

Common GC algorithms include: mark-sweep (mark reachable objects from roots, sweep unreachable ones), generational collection (objects are segregated by age; young objects are collected frequently, old objects less so), reference counting (each object tracks how many references point to it; count reaches zero → reclaim), and tracing (traverse object graph from roots). Modern GCs (JVM, .NET CLR, V8) use generational mark-sweep combined with concurrent/parallel collection to minimize pauses.

Real-world analogy. Garbage collection is like a hotel housekeeping service. Instead of guests removing their own trash (manual memory management), housekeeping comes daily (minor GC) to empty bins in occupied rooms. Weekly, they do a deep clean (major GC), checking storage closets and under beds for forgotten items. Guests never think about trash removal.

Example (GC in C# — IDisposable for managed resources):

// GC handles memory automatically
var list = new List<string>();
list.Add("Hello");
// When 'list' goes out of scope, GC reclaims the memory

Related terms: RAII, JVM, CLR, V8 Engine, AOT Compilation

Related tutorial: Garbage Collection Explained