Services
Technology Web App Development Mobile App Development Windows App Development Database Development UI/UX Development Cloud Development SEO Digital Marketing Guest Posting Content Writing Artificial Intelligence Data Science ERP Development CRM Development CMS Development LMS Development Business Listing Blockchain Technology Startup Promotion
Products
Data Converter Cleaner TUC - Unit Converter Import Export Survey Manager Tweet Controller
Developer
Article Blog Forum Interview Beginner News Startup Quiz
Users
Career
Apply Job Internship
Pricing
Login Sign Up Get a Quote

forum

home / developersection / forums / how does garbage collection work in .net clr?
Ask Question

How does garbage collection work in .NET CLR?

Ravi Vishwakarma 518 16 Jun 2025

How does garbage collection work in .NET CLR with example?

c# c#
Updated 19 Jun 2025
Ravi Vishwakarma
Ravi Vishwakarma

IT-Hardware & Networking

Ravi Vishwakarma is a dedicated Software Developer with a passion for crafting efficient and innovative solutions. With a keen eye for detail and years of experience, he excels in developing robust software systems that meet client needs. His expertise spans across multiple programming languages and technologies, making him a valuable asset in any software development project.

Message

1 Answers

Anubhav Sharma
Anubhav Sharma 19 Jun 2025
Report Abuse

Garbage Collection (GC) in the .NET CLR (Common Language Runtime) is an automatic memory management system that reclaims memory occupied by objects no longer in use, freeing developers from manually releasing memory (like in C/C++).

Key Concepts of .NET Garbage Collection

1. Managed Heap

  • All reference types are allocated on the managed heap.
  • The CLR tracks object references and cleans up memory when objects are no longer accessible.

2. Generational GC

The heap is divided into three generations:

Generation Description Purpose
Gen 0 Short-lived objects Frequently collected
Gen 1 Buffer between Gen 0 and Gen 2 Less frequently collected
Gen 2 Long-lived objects (e.g., static data, caches) Least frequently collected

Most new objects start in Gen 0. If they survive collections, they move up (get promoted) to higher generations.

3. Collection Process

When memory runs low or thresholds are hit:

  • GC checks which objects are still reachable from:
    • Stack
    • Static fields
    • CPU registers
  • Unreachable objects are considered garbage.
  • GC:
    • Calls finalizers (if any).
    • Frees memory.
    • Compacts the heap to reduce fragmentation (except for large object heap in older .NET versions).

4. Large Object Heap (LOH)

  • Objects > 85 KB are stored in LOH.
  • Collected only during Gen 2 collections.
  • Was not compacted before .NET 4.5+ (now optional).

5. GC Modes

Mode Description Use Case
Workstation GC Optimized for low-latency desktop apps UI apps
Server GC Optimized for throughput and scalability ASP.NET, backend services
Background GC Collects Gen 2 concurrently with app execution Reduces pause times

6. Finalization and IDisposable

  • GC may call an object’s finalizer before reclaiming its memory.
  • Finalizers delay collection (object survives an extra cycle).
  • IDisposable and using are preferred for deterministic cleanup of unmanaged resources.

Performance Optimizations by GC

  • Object promotion: Older objects are collected less often.
  • Compaction: Reduces fragmentation by moving objects.
  • Pinned memory: Avoid moving interop objects (e.g., fixed buffers).
  • GC pressure: Monitored to tune allocations (e.g., GC.GetTotalMemory()).

Summary

Feature Description
Automatic No manual free() needed
Generational Groups objects by lifetime
Compacting Reorganizes memory to prevent fragmentation
Safe Avoids dangling pointers and memory leaks (in managed code)
Modes Workstation, Server, Background

Garbage collection in .NET CLR is safe, efficient, and optimized for a wide range of applications — from desktop to web servers — letting developers focus on logic rather than memory management.

advertising