Working set larger than Heap size reported by CLR Debug

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an app. CLR Debug says the heap is 3.5MB. perfmon says that working
set size is 52MB.

Where's the unreported amount and how can I inspet it?
 
The managed heap is only a (small) part of the working set. The remaining
part is taken by the CLR runtime code, the C runtime library, the unmanaged
heap, the commited stack space.

Willy.
 
Thanks... So how can I inspect it? :-)

Willy Denoyette said:
The managed heap is only a (small) part of the working set. The remaining
part is taken by the CLR runtime code, the C runtime library, the unmanaged
heap, the commited stack space.

Willy.
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

CLR Profiler Question 1
Virtual Bytes vs Private Bytes 1
Stack size problem with managed code 2
Is new & free in CLR heap fast? 1
Problem running with the /CLR flag 1
Monitoring and debugging applications 2
w3wp.exe (ASP .Net) eating memory 3
CLR doesn't do warm start? 1

Back
Top