c# - Why does the sum of objects in !DumpHeap -stat not match !EEHeap -gc? -


i'm looking @ full application dump in windbg, , trying understand memory being consumed.

i've parsed output of !dumpheap -stat , summed total memory in report, getting ~7 gb. comparison, if run !eeheap -gc, reports total of ~11 gb.

why there such big difference between 2 reports? how can find out additional 4 gb going?

the value of !eeheap sum of segment sizes allocated .net.

this value larger sum of output of !dumpheap. in cases differs because there few objects in segments, e.g. pinned objects, used native pinvoke or com interop stuff. can prevent .net releasing segments. can check pinned objects !gchandles.

cross check value of !eeheap against <unknown> value reported !address -summary. assuming have no native code calls vitualalloc() directly , don't use msxml, value of !eeheap should close that.


Comments

Popular posts from this blog

javascript - Chart.js (Radar Chart) different scaleLineColor for each scaleLine -

apache - Error with PHP mail(): Multiple or malformed newlines found in additional_header -

java - Android – MapFragment overlay button shadow, just like MyLocation button -