Cor,
Thanks for the info. After reading a bunch of posts in this and the
performance new group I realized I am not the only one to look at this
improperly.
I understand that the GC will collect when it comes down to a memory crunch,
but my specific concern is that this is running on the terminal server. If
each session allocates this memory to itself and does not share it across
the sessions, then 30 users running a 125 in their heap will tie up 3.7Gig I
have 4GB in these terminal servers but that doesn't leave a lot of room.
Anyone have experience with this specific situation?
Also I am calling the dispose and close methods of everything that I can on
the MDIChild close, there are no references to anything in the MDIChild on
the parent.
One other thing that I noticed when I run the Allocation Profiler, is that
there are a lot of assemblies called in the MDI child that are still open
when I close that child.
Is there any way to force these assemblies to unload or does .Net hold them
open for better performance on the next run?
I appreciate the input.
Thanks,
Justin
"Cor Ligthert [MVP]" <no************@planet.nl> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Justin,
All what you tell does not free any memory.
An object is released if it has not any reference anymore to something or
that there is nothing referencing it anymore.
That is what the GC checks to release it. Calling the GC thousand times
does nothing more than eating processing time, if that condition is not
fullfilled.
(Although you should not rely on the taskmanager the information given in
that says nothing, see some of the messages from Willy in this newsgroup)
http://groups-beta.google.com/group/...rch+this+group
I hope this helps,
Cor