Application memory usage

[Crirus]

I have an aplication (obviously )
I look at the Task Manager, memory usage column and notice the following:

First time I start the application, I have around 55.000- 60.000 K.
After I minimise the application and restore, the Memory usage drop to
16.000K and remain around that value..
Should I be concerned with this?

 

[Blumidoo]

I have an aplication (obviously )

I look at the Task Manager, memory usage column and notice the following:

First time I start the application, I have around 55.000- 60.000 K.
After I minimise the application and restore, the Memory usage drop to
16.000K and remain around that value..
Should I be concerned with this?

Nothing to worry about, this is how .NET Framework works.

You might want to browse through the
microsoft.public.dotnet.framework.performance archives on
Google for the big collection of posts on the topic.

sincerely,
--
Sebastian Zaklada
Skilled Software
http://www.skilledsoftware.com
************************************
SQL Source Control 2003 - for
SQL Server Source Safe integration
and custom databases documentation

 

[Crirus]

I still like to get some explanation on this... kind of courious...

 

[Crirus]

OK, found all details.. thanks

 

[Herfried K. Wagner [MVP]]

I have an aplication (obviously )
I look at the Task Manager, memory usage column and notice the following:

First time I start the application, I have around 55.000- 60.000 K.
After I minimise the application and restore, the Memory usage drop to
16.000K and remain around that value..
Should I be concerned with this?

This behavior is not specific to .NET applications only.

It is a feature of the Windows/Explorer shell.

If an application is minimized, Windows removes the working set memory from
the application by calling the Win32 function 'SetProcessWorkingSetSize':

<http://msdn.microsoft.com/library/en-us/dllproc/base/setprocessworkingsetsize.asp>

Windows supposes that minimized applications will not be used for some time
and this memory will be made available to other processes.

When restoring the window the application gets the memory back:

<http://support.microsoft.com/?kbid=293215>

This behavior is by design and it doesn't make sense to worry about it.