Home/ Questions/Q 8247287
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T22:47:44+00:00

Confused by private bytes! Currently analysing the memory usage of our C# .NET application

  • 0

Confused by private bytes!

Currently analysing the memory usage of our C# .NET application with ANTS profiler. Here are our findings taken after start-up with the main form visible on screen. No other functionality has been used.

Gen 0 Heap – 5.8MB
Gen 1 Heap – 2.5MB
Gen 2 Heap – 13.9MB
Bytes in all Heaps – 17MB
Large Object Heap – 0.7MB
Private Bytes – 130MB
Working Set – 150MB

If the bytes in all heaps is only 17MB why do we have such a large private bytes allocation? Are private bytes allocated by the system or does private bytes start at zero expanded as it get’s filled by the software? i.e. is private bytes a bubble which may in fact only be partially used? If so, what determines it’s size?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Private bytes are all the virtual allocations of a process that cannot be shared with other processes (ie. excludes code and memory mapped files). This will include all NT (native) Heaps, any managed Heap, stacks and any memory explictly allocated by applicatio (VirtualAlocEx).

    You can use !dumpheap -stat to get a detailed usage of your CLR memory usage. See CLR Memory Leak

    • 0