Yeah, it seems like a lot. The virtual machine is heavy. But IMHO people
tend to give too much weight to what Task Manager tells them. AFAIK, the mem
usage reported includes memory *mapped* into the process (meaning it's not
part of the process proper). Meaning if you have two .NET exe's running...
they both say 8mb.... but really 4 of those 8 megs is claimed by the runtime
and is shared between the two (little known fact: the *executable binary
image* of DLL's in memory is always shared across processes... even on
NT/2K/XP!) meaning they only really occupy about 12 megs of actual RAM.
Before someone jumps up to note the process seperations on NT based Windows
without really understanding how it works (note I said *exectuable image*
NOT *storage* space- heaps or stacks) , see article Q100635 in MSKB or MSDN.
"Éric Lapointe" <Er***********@usherbrooke.ca> wrote in message
news:op**************@satellite2450.civil.usherbro oke.ca...
But... * meg... there is a way to optimize that ?
Éric
On 14 Jun 2004 20:41:46 +0200, Herfried K. Wagner [MVP]
<hi***************@gmx.at> wrote:
* =?iso-8859-15?Q?=C9ric_Lapointe?= <Er***********@usherbrooke.ca>
scripsit: I create a simple windows form with a textbox.
In Process information window of WindowsXP, my application eat 8,88
meg of memory
IT IS A LOT ! it is normal ?
Yes.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/