"Dave" <Dave@discussions.microsoft.com> wrote in message
news:F0798392-FA5E-4845-B032-C43E203B08D0@microsoft.com...
> I've been experimenting with the memory footprint of a windows app and
I've
> come across some odd behaviour, which I'd appreciate some comments on from
> someone who knows about these things.
> Starting with a basic form app as generated by VS, with a single button -
> nothing in the button click handler yet. This runs at about 8Mb memory, as
> measured by task manager.
> When minimised by the user this drops dramatically to 1M or under.
> Putting WindowState=FormWindowState.Minimized; in the button handler has
> pretty much the same effect, down to 1M or less when the button is
pressed.
> Putting Hide() in the button handler has no effect on the footprint at
all.
> Moving the WindowState=FormWindowState.Minimized; from the button handler
to
> the Form.Load event reduces the memory, but only to about 4M.
> Moving the WindowState=FormWindowState.Minimized; to the constructor has
no
> effect on the footprint at all.
> This behaviour is very puzzling. I am writing an invisible application ie.
> one which, under most circumstances, has no UI at all (there are reasons
why
> it shouldn't be a service, before you ask<g>). I am trying to get the
> resource usage as low as possible for this. Any comments/suggestions would
be
> welcome.
> --
> Dave

"Dave" <Dave@discussions.microsoft.com> wrote in message
news:F0798392-FA5E-4845-B032-C43E203B08D0@microsoft.com...
> I've been experimenting with the memory footprint of a windows app and
> I've
> come across some odd behaviour, which I'd appreciate some comments on from
> someone who knows about these things.
> Starting with a basic form app as generated by VS, with a single button -
> nothing in the button click handler yet. This runs at about 8Mb memory, as
> measured by task manager.
> When minimised by the user this drops dramatically to 1M or under.
> Putting WindowState=FormWindowState.Minimized; in the button handler has
> pretty much the same effect, down to 1M or less when the button is
> pressed.
> Putting Hide() in the button handler has no effect on the footprint at
> all.
> Moving the WindowState=FormWindowState.Minimized; from the button handler
> to
> the Form.Load event reduces the memory, but only to about 4M.
> Moving the WindowState=FormWindowState.Minimized; to the constructor has
> no
> effect on the footprint at all.
> This behaviour is very puzzling. I am writing an invisible application ie.
> one which, under most circumstances, has no UI at all (there are reasons
> why
> it shouldn't be a service, before you ask<g>). I am trying to get the
> resource usage as low as possible for this. Any comments/suggestions would
> be
> welcome.
> --
> Dave

"Harald Ums" wrote:

> It's called workingset trimming - every windows process does this not just
> net processes: just minimize internet explorer and watch the counters
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:F0798392-FA5E-4845-B032-C43E203B08D0@microsoft.com...
> > I've been experimenting with the memory footprint of a windows app and
> > I've
> > come across some odd behaviour, which I'd appreciate some comments on from
> > someone who knows about these things.
> > Starting with a basic form app as generated by VS, with a single button -
> > nothing in the button click handler yet. This runs at about 8Mb memory, as
> > measured by task manager.
> > When minimised by the user this drops dramatically to 1M or under.
> > Putting WindowState=FormWindowState.Minimized; in the button handler has
> > pretty much the same effect, down to 1M or less when the button is
> > pressed.
> > Putting Hide() in the button handler has no effect on the footprint at
> > all.
> > Moving the WindowState=FormWindowState.Minimized; from the button handler
> > to
> > the Form.Load event reduces the memory, but only to about 4M.
> > Moving the WindowState=FormWindowState.Minimized; to the constructor has
> > no
> > effect on the footprint at all.
> > This behaviour is very puzzling. I am writing an invisible application ie.
> > one which, under most circumstances, has no UI at all (there are reasons
> > why
> > it shouldn't be a service, before you ask<g>). I am trying to get the
> > resource usage as low as possible for this. Any comments/suggestions would
> > be
> > welcome.
> > --
> > Dave
>
>