Why Dumping a .NET Process Increases Memory Usage -
We have a .NET service using ~ 30 MB of memory at startup. (VM ~ use mem =)
I dump this process and what those 30MB
CDB debugger generated mini dump increased mem usage by 100 MB . From the dump - I can see (DLLs) those were 100 MB image memory
----------- ----- ---- Usage Summary -------------------------- Tot Siez (KB) PCT (Totes) PCT (Busy) Use 2d07000 (46108) : 20.02% 28.45% Kshetrupyog Aisaviadi 761 C 1000 (1 9 35024): 92.27% 00:00% Kshetrupyogi 64 B-0000 (103104): 04.92% 63.62% Kshetrupyog Ayoji 900000 (9216): 00:44% 05.69% Kshetrugstakt 9000 ( 36): 00.00% 00.02%: RegionUsageTeb 380000 (3584): 00.17% 02.21%: RegionUsageHeap 0 (0): 00.00% 00.00%: RegionUsagePageHeap 1000 (4): 00.00% 00.00%: RegionUsagePeb 1000 (4) : 00.00% 00.00%: RegionUsageProcessParametrs 2 000 (8): 00.00% 00.00%: Re GionUsageEnvironmentBlock Tot: 7fff0000 (2,097,088 KB) Busy: 09e44000 (162,064 KB) mem use is high left, long after the debugger is different I know what this image Want to have load / memory enhancement cover?
Thank you.
"Usually, unused pages are not part of the working set, unless only the location of the address. Creating a full dump, reading all the pages in the address space, and writing it on the disk. The size of the dump is basically the size of the address space of the process, which is expected of your description. "
I got the answer.
Comments
Post a Comment