memory consumption!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

We built a Windows application on .Net 2 framework using Infragistics
controls. We got a bug reported from our client complaining high physical
memory consumption showing in the task manager and the memory suddenly drops
off as they minimize the application. As we analysed the problem we could
find the application seems to consume 55000K and drops off to 3000K as I
minimize the application, but the strange thing I noiticed is that this seems
to happen for most of the Windows application like IE, Media Player,outlook
or even for MS Word.

I would like to know how can I address this bug and also why such a
phenomenon haoning in windows.

Is it due to the video memory used by the application? which may released as
I minimize?

please post your comments and resolutions.

Thanks
 
We built a Windows application on .Net 2 framework using Infragistics
controls. We got a bug reported from our client complaining high physical
memory consumption showing in the task manager and the memory suddenly drops
off as they minimize the application. As we analysed the problem we could
find the application seems to consume 55000K and drops off to 3000K as I
minimize the application, but the strange thing I noiticed is that this seems
to happen for most of the Windows application like IE, Media Player,outlook
or even for MS Word.

I would like to know how can I address this bug and also why such a
phenomenon haoning in windows.

Is it due to the video memory used by the application? which may released as
I minimize?

This is not a bug and this has little to do with the .NET framework itself
as you have already noticed. This is due to the way the Windows Task
Manager presents the memory usage (the memory usage that you see in task
manager is not the actual memory being used by the application itelf).
Michael McIntyre has written a very good article about this particular
"problem":
<http://getdotnetco.web119.discountasp.net/GdncStore/free/Articles/The Memory Mystery.htm>
(see the ".Net Urban Legend" section).
 
Good Read.

-Thanks.

M.

Mehdi said:
This is not a bug and this has little to do with the .NET framework itself
as you have already noticed. This is due to the way the Windows Task
Manager presents the memory usage (the memory usage that you see in task
manager is not the actual memory being used by the application itelf).
Michael McIntyre has written a very good article about this particular
"problem":
<http://getdotnetco.web119.discountasp.net/GdncStore/free/Articles/The Memory Mystery.htm>
(see the ".Net Urban Legend" section).
 
Back
Top