.Net is a pig

[Mike Peretz]

I have tried everything to make .NET return memory to the OS. I use Dispose
and GC.Collect() as much as possible. I understand that if the memory is
available then why not take it and keep it. However, I noticed that memory
is only returned to the OS when the machine is desperate for RAM, but at
that point it is way too late, the OS is swapping and everything becomes
very slow. The other case where memory is returned to the OS is when I
minimize the application. According to Microsoft Documentation, the process
working size is trimmed, causing memory to be cashed or to be returned to
the OS.

Don't get me wrong, I understand that .NET is like an OS and needs to manage
its own heaps and that is not cheap by any means. But! For the love of God,
my little windows application with an Access connection is just consuming
more and more memory every time I click on a new option. On average, it
starts with 20M and can grow to 40M. Nothing, except minimizing the
application seems to work. This can not be acceptable, am I the only one
that noticed this?

[Nasser]

Did you try

myObject = null;

Thanks.
Nasser.

-----Original Message-----
I have tried everything to make .NET return memory to the OS. I use Disposeand GC.Collect() as much as possible. I understand that if the memory isavailable then why not take it and keep it. However, I noticed that memoryis only returned to the OS when the machine is desperate for RAM, but atthat point it is way too late, the OS is swapping and everything becomesvery slow. The other case where memory is returned to the OS is when Iminimize the application. According to Microsoft Documentation, the processworking size is trimmed, causing memory to be cashed or to be returned tothe OS.

Don't get me wrong, I understand that .NET is like an OS and needs to manageits own heaps and that is not cheap by any means. But! For the love of God,my little windows application with an Access connection is just consumingmore and more memory every time I click on a new option. On average, itstarts with 20M and can grow to 40M. Nothing, except minimizing theapplication seems to work. This can not be acceptable, am I the only onethat noticed this?
.

[Mike Peretz]

Yes. I even use a reference counting program to make sure there are no
unused references...
"Nasser" <an*******@discussions.microsoft.com> wrote in message
news:06****************************@phx.gbl...

Did you try

myObject = null;

Thanks.
Nasser.

-----Original Message-----
I have tried everything to make .NET return memory to

the OS. I use Dispose

and GC.Collect() as much as possible. I understand that

if the memory is

available then why not take it and keep it. However, I

noticed that memory

is only returned to the OS when the machine is desperate

for RAM, but at

that point it is way too late, the OS is swapping and

everything becomes

very slow. The other case where memory is returned to

the OS is when I

minimize the application. According to Microsoft

Documentation, the process

working size is trimmed, causing memory to be cashed or

to be returned to

the OS.

Don't get me wrong, I understand that .NET is like an OS

and needs to manage

its own heaps and that is not cheap by any means. But!

For the love of God,

my little windows application with an Access connection

is just consuming

more and more memory every time I click on a new option.

On average, it

starts with 20M and can grow to 40M. Nothing, except

minimizing the

application seems to work. This can not be acceptable,

am I the only one

that noticed this?
.

[Charles]

You could try forcing the garbage collector to run at
specific times by calling
void GC.Collect method.

-----Original Message-----
Yes. I even use a reference counting program to make sure there are nounused references...
"Nasser" <an*******@discussions.microsoft.com> wrote in messagenews:06****************************@phx.gbl...

Did you try

myObject = null;

Thanks.
Nasser.

>-----Original Message-----
>I have tried everything to make .NET return memory to

the OS. I use Dispose

>and GC.Collect() as much as possible. I understand that

if the memory is

>available then why not take it and keep it. However, I

noticed that memory

>is only returned to the OS when the machine is

desperate for RAM, but at

>that point it is way too late, the OS is swapping and

everything becomes

>very slow. The other case where memory is returned to

the OS is when I

>minimize the application. According to Microsoft

Documentation, the process

>working size is trimmed, causing memory to be cashed or

to be returned to

>the OS.
>
>
>
>Don't get me wrong, I understand that .NET is like an

OS and needs to manage

>its own heaps and that is not cheap by any means. But!

For the love of God,

>my little windows application with an Access connection

is just consuming

>more and more memory every time I click on a new

option. On average, it

>starts with 20M and can grow to 40M. Nothing, except

minimizing the

>application seems to work. This can not be acceptable,

am I the only one

>that noticed this?
>
>
>.
>

.

[Matthew W. Jackson]

I'm optimistically assuming that your newsgroup server has lost the original
post, because the poster clearly stated that he had tried that (among other
things)

If that IS the case, you should probably be using Microsoft's news servers
for these newsgroups, as they keep messages around for quite a while. Just
some (hopefully) helpful advice...I'm on Time Warner and their news severs
are TERRIBLE, and moving to Microsoft's for their newsgroups helped out
enormously.

If that's NOT the case, then I guess we'll have to forgive you (this time).

"Charles" <a@b.c> wrote in message
news:0a****************************@phx.gbl...

You could try forcing the garbage collector to run at
specific times by calling
void GC.Collect method.

-----Original Message-----
Yes. I even use a reference counting program to make sure

there are no

unused references...
"Nasser" <an*******@discussions.microsoft.com> wrote in

message

news:06****************************@phx.gbl...

Did you try

myObject = null;

Thanks.
Nasser.
>-----Original Message-----
>I have tried everything to make .NET return memory to
the OS. I use Dispose
>and GC.Collect() as much as possible. I understand that
if the memory is
>available then why not take it and keep it. However, I
noticed that memory
>is only returned to the OS when the machine is desperate for RAM, but at
>that point it is way too late, the OS is swapping and
everything becomes
>very slow. The other case where memory is returned to
the OS is when I
>minimize the application. According to Microsoft
Documentation, the process
>working size is trimmed, causing memory to be cashed or
to be returned to
>the OS.
>
>
>
>Don't get me wrong, I understand that .NET is like an OS and needs to manage
>its own heaps and that is not cheap by any means. But!
For the love of God,
>my little windows application with an Access connection
is just consuming
>more and more memory every time I click on a new option. On average, it
>starts with 20M and can grow to 40M. Nothing, except
minimizing the
>application seems to work. This can not be acceptable,
am I the only one
>that noticed this?
>
>
>.
>

.

[Greg Beech [MSFT]]

Please do not call GC.Collect() in the hope that you will benefit either
memory management or your applications performance - you won't - you will
in fact cripple it. The GC is self tuning and will optimise memory
collection based on the applications memory usage and requirements.
Calling GC.Collect() yourself may even contribute to the high memory usage,
believe it or not! Rule of thumb - *never* call GC.Collect(). Not quite
sure what you mean by a reference counting program - .NET does not use
reference counting for its memory management.

Note that the memory usage indicated by the application is not real used
memory, it is memory the CLR has provisionally allocated for use in a
contiguous block, and which it will readily release back to the OS if it
becomes short, as much of this memory is unused. On a workstation the GC
will allow memory to be consumed (more than the server model for
multi-processor boxes) to keep the user experience better by not
interrupting the application so much, but will collect if the OS runs short.

Cheers,

Greg

This posting is provided "AS IS"with no warranties, and confers no rights.

[Robert Manookian]

Have you tried:
SetProcessWorkingSetSize(Process.GetCurrentProcess .Handle.ToInt32, -1, -1)

"Charles" <a@b.c> wrote in message
news:0a****************************@phx.gbl...

You could try forcing the garbage collector to run at
specific times by calling
void GC.Collect method.

-----Original Message-----
Yes. I even use a reference counting program to make sure

there are no

unused references...
"Nasser" <an*******@discussions.microsoft.com> wrote in

message

news:06****************************@phx.gbl...

Did you try

myObject = null;

Thanks.
Nasser.
>-----Original Message-----
>I have tried everything to make .NET return memory to
the OS. I use Dispose
>and GC.Collect() as much as possible. I understand that
if the memory is
>available then why not take it and keep it. However, I
noticed that memory
>is only returned to the OS when the machine is desperate for RAM, but at
>that point it is way too late, the OS is swapping and
everything becomes
>very slow. The other case where memory is returned to
the OS is when I
>minimize the application. According to Microsoft
Documentation, the process
>working size is trimmed, causing memory to be cashed or
to be returned to
>the OS.
>
>
>
>Don't get me wrong, I understand that .NET is like an OS and needs to manage
>its own heaps and that is not cheap by any means. But!
For the love of God,
>my little windows application with an Access connection
is just consuming
>more and more memory every time I click on a new option. On average, it
>starts with 20M and can grow to 40M. Nothing, except
minimizing the
>application seems to work. This can not be acceptable,
am I the only one
>that noticed this?
>
>
>.
>

.