The CDB/Windbg debugger generating the mini-dump increased mem usage by 100MB.
From the dump I could see those 100MB were image memory (DLLs)
-------------------- Usage SUMMARY --------------------------
TotSize ( KB) Pct(Tots) Pct(Busy) Usage
2d07000 ( 46108) : 02.20% 28.45% : RegionUsageIsVAD
761ac000 ( 1935024) : 92.27% 00.00% : RegionUsageFree
64b0000 ( 103104) : 04.92% 63.62% : RegionUsageImage
900000 ( 9216) : 00.44% 05.69% : RegionUsageStack
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
2000 ( 8) : 00.00% 00.00% : RegionUsageEnvironmentBlock
Tot: 7fff0000 (2097088 KB) Busy: 09e44000 (162064 KB)
The mem usage is left high, long after the debugger detached. I want to know
what is casing this image load / memory raise?
Thanks.
--
Tal.
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Tal" <T...@newsgroups.nospam> wrote in message
news:28BA3AF0-CF72-4E40...@microsoft.com...
--
Tal.
"Ivan Brugiolo [MSFT]" wrote:
> .
>
Probably because the system still has plenty of free memory. If you run
a memory intensive app these pages should get trimmed.
--
Pavel Lebedinsky/Windows Fundamentals Test
--
Tal.
"Pavel Lebedinsky [MSFT]" wrote:
> .
>