Memory Usage

[Stephajn Craig]

Hi all,

I wrote a tiny little Windows Forms application that periodically checks
a database for certain conditions and then pops up a message box asking if
you want to do something about those conditions. It runs in the system
tray. I find that when I start this program, it automatically eats up 11 MB
of memory on my machine. When the prompt appears, that climbs to 17 MB.

If a user answers yes to the prompt, it will open another window that
has a web browser control built onto it. (This is just the old web browser
control that I would have used if I had built the thing using VB6) So an
Interop assembly exists as well. When this form loads, memory usage jumps
to 36 MB. This is craziness since the application is so small and simple.

Is it normal for a VB application built using .NET to take this much
memory? I even tried tunning other VB.NET apps that are shipped as samples,
and their initial memory usage seems to be a bit high as well. My
supervisor saw this and wants an explanation. Best I could offer is that
this extra memory is for the Just-In-Time compilation and the managed
environment we get with .NET. Is this true?

Stephajn

 

[Andre Nogueira]

Hi there! See my post on that topic. It was posted on 13-01-2004 at 15.21.
I didn't copy and paste because there were several answers.
Hope it helps!

Andre Nogueira

 

[Stephajn Craig]

Well that answers that question about the IE Control, but what about before
that's loaded? My application, without doing anything but running a Windows
Forms Timer control is eating up 17 MB of RAM. that seems a bit much. (Or
does it?)

Stephajn

 

[Herfried K. Wagner [MVP]]

Well that answers that question about the IE Control, but what about before
that's loaded? My application, without doing anything but running a Windows
Forms Timer control is eating up 17 MB of RAM. that seems a bit much. (Or
does it?)

I think that's still normal if the memory usage is not increasing from
time to time (maybe memory leak).