Menmorymanagement

[Thorsten]

Hi all

according to the taskmanager my vb.net application grows continually in memory usage. Obviously the memory used by mdi children and SqlConnections and/or DataTables which are closed is not released. Even the close-event (Me.Close) of an mdi-child needs approx 500 kb (sometimes more sometimes less). dispose or the manual calling of the garbage collector has no effect
Are there any settings concerning the garbage collector or any other possibilities to release memory manulally

Thank you in advance
Thorsten

[Cor Ligthert]

Hi Thorsten,

When you search the dotnet newsgroup about taskmanager and memory than you
will see only one response.

Do not trust the memory which it reported by taskmanager with dotNet
programs.

I hope this helps?

Cor

[Cor Ligthert]

Hi Thorsten,

When you search the dotnet newsgroup about taskmanager and memory than you
will see only one response.

Do not trust the memory which it reported by taskmanager with dotNet
programs.

I hope this helps?

Cor

[Steve McLellan]

"Cor Ligthert" <no**********@planet.nl> wrote in message
news:ee**************@TK2MSFTNGP10.phx.gbl...

Hi Thorsten,

When you search the dotnet newsgroup about taskmanager and memory than you
will see only one response.

Do not trust the memory which it reported by taskmanager with dotNet
programs.

I hope this helps?

Cor

Unfortunately, users will. Are there any plans you know of to correct this
problem?

Steve

[Steve McLellan]

"Cor Ligthert" <no**********@planet.nl> wrote in message
news:ee**************@TK2MSFTNGP10.phx.gbl...

Hi Thorsten,

When you search the dotnet newsgroup about taskmanager and memory than you
will see only one response.

Do not trust the memory which it reported by taskmanager with dotNet
programs.

I hope this helps?

Cor

Unfortunately, users will. Are there any plans you know of to correct this
problem?

Steve

[Willy Denoyette [MVP]]

The values shown by the taskmanager are correct, these are the same values
as presented by the performance manage (perfmon) and are the values taken
from the various OS perfcounters.
The only problem is that taskmanager's memory counter names are not the same
as used in perfmon, and this confuses people, but the values are correct,
also the number of counters is very restricted, therefore you should use
perfmon for diagnosing memory problems.
f.i 'Mem usage' is in reality the 'Working Set' and 'VM Size' is 'Private
Bytes'.
Willy.
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:ee**************@TK2MSFTNGP10.phx.gbl...

Hi Thorsten,

When you search the dotnet newsgroup about taskmanager and memory than you
will see only one response.

Do not trust the memory which it reported by taskmanager with dotNet
programs.

I hope this helps?

Cor

[Willy Denoyette [MVP]]

The values shown by the taskmanager are correct, these are the same values
as presented by the performance manage (perfmon) and are the values taken
from the various OS perfcounters.
The only problem is that taskmanager's memory counter names are not the same
as used in perfmon, and this confuses people, but the values are correct,
also the number of counters is very restricted, therefore you should use
perfmon for diagnosing memory problems.
f.i 'Mem usage' is in reality the 'Working Set' and 'VM Size' is 'Private
Bytes'.
Willy.
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:ee**************@TK2MSFTNGP10.phx.gbl...

Hi Thorsten,

When you search the dotnet newsgroup about taskmanager and memory than you
will see only one response.

Do not trust the memory which it reported by taskmanager with dotNet
programs.

I hope this helps?

Cor

[Cor Ligthert]

Hi Willy,

Do you know who wrote this.

http://tinyurl.com/2oc9a

:-)

Cor

[Cor Ligthert]

Hi Willy,

Do you know who wrote this.

http://tinyurl.com/2oc9a

:-)

Cor

[Willy Denoyette [MVP]]

Hi Cor,
Sure, I did, but IMO I didn't say the taskmanager's counters were wrong, I
only said you need to use the perfmon counters if you need a consistent view
of the CLR memory counters. The taskmanager's has only very basic (but
correct) process memory counters (Working Set and Private Bytes), and no CLR
counters.
Also note that taskman is an end user tool, and MSFT thought they should
change the names of the counters into something that an average user would
understand ('Mem usage' and 'VM Size).
I for one wished taskman had an expert mode or did not show these counters
as they tend to confuse people.

Willy.
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...

Hi Willy,

Do you know who wrote this.

http://tinyurl.com/2oc9a

:-)

Cor

[Willy Denoyette [MVP]]

Hi Cor,
Sure, I did, but IMO I didn't say the taskmanager's counters were wrong, I
only said you need to use the perfmon counters if you need a consistent view
of the CLR memory counters. The taskmanager's has only very basic (but
correct) process memory counters (Working Set and Private Bytes), and no CLR
counters.
Also note that taskman is an end user tool, and MSFT thought they should
change the names of the counters into something that an average user would
understand ('Mem usage' and 'VM Size).
I for one wished taskman had an expert mode or did not show these counters
as they tend to confuse people.

Willy.
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...

Hi Willy,

Do you know who wrote this.

http://tinyurl.com/2oc9a

:-)

Cor

[Cor Ligthert]

Hi Willy,

That was all I did wanted to say in my first messsage to the OP, do not
trust on the taskmanager when you make your decissions about memory use.

Cor

[Cor Ligthert]

Hi Willy,

That was all I did wanted to say in my first messsage to the OP, do not
trust on the taskmanager when you make your decissions about memory use.

Cor