(Type your message here)

--------------------------------
From: John Stephens
Hi Naill,
Did you ever determine what the cause of the memory retention=
your app? I'm writing a =2ENet add-on to a MFC app=2E The clr heap=
always stays small (1-7MB), and I have most of the code NGen'ed=
and Gac'ed so it will be shared across users=2E If I load all=
components, the working set will never drop below 60MB (25 MB is=
shared code)=2E The managed heap drops, but 10+MB still show as=
"Other Data" under VAdump=2E If I close all components, and then=
reopen, it (thankfully!) never goes above 60MB=2E Any ideas? I=
have looked everywhere and I mean everywhere!

-----------------------
Posted by a user from =2ENET 247 (http://www=2Edotnet247=2Ecom/)

[quoted text, click to view]

Have a look at this page for more details on the memory mystery.

http://getdotnetco.web101.discountasp.net/GdncStore/free/Articles/The%20Memory%20Mystery.htm

Hi John,

[quoted text, click to view]

to the best of my knowledge this means they all share the same assembly, but
this is, for each appdomain/process, still loaded into memory separately.

"John Stephens via .NET 247" <anonymous@dotnet247.com> schrieb im
Newsbeitrag news:emajAnYMFHA.2680@TK2MSFTNGP09.phx.gbl...
(Type your message here)

--------------------------------
From: John Stephens
Hi Naill,
Did you ever determine what the cause of the memory retention your app? I'm
writing a .Net add-on to a MFC app. The clr heap always stays small (1-7MB),
and I have most of the code NGen'ed and Gac'ed so it will be shared across
users. If I load all components, the working set will never drop below 60MB
(25 MB is shared code). The managed heap drops, but 10+MB still show as
"Other Data" under VAdump. If I close all components, and then reopen, it
(thankfully!) never goes above 60MB. Any ideas? I have looked everywhere and
I mean everywhere!

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>1UI2NHi4TkWWV6zD8h+XWQ==</Id>

[quoted text, click to view]

Yes, unless they're loaded domain-neutral. Domain-neutral assemblies are
only loaded once per process, but they have separate data on a per-app
domain basis.

[quoted text, click to view]