ID memory leak

[Fitz]

I'm running WinXP Pro. I like to know how to identify to source of a memory
leak. I have 1GB of RAM. After bootup, I'm using about 275MB of RAM for XP
and running task. After using the computer for awhile, regardless of
program, that will increase to over 450MB with everything closed and back to
desktop. Does this sound like a memory leak, and if so, how do I identify
the program/process that is causing it?

Thanks,
Fitz

 

[Detlev Dreyer]

I'm running WinXP Pro. I like to know how to identify to source of a
memory leak. I have 1GB of RAM. After bootup, I'm using about 275MB of
RAM for XP and running task. After using the computer for awhile,
regardless of program, that will increase to over 450MB with
everything closed and back to desktop.

If SP1 installed, you may want to read
"Heap Algorithm Update for Atypically Large Heap Requests"
http://support.microsoft.com/kb/815411/en-us

Make also sure that you didn't disable virtual memory.

Does this sound like a memory leak,

Not really. See also http://aumha.org/win5/a/xpvm.php
Since having 1GB of RAM installed, you shouldn't worry too
much about memory management. Note that unused RAM is wasted RAM.

 

[Sleepless in Seattle]

A fantasy in your own mind.

 

[Ron Martell]

I'm running WinXP Pro. I like to know how to identify to source of a memory
leak. I have 1GB of RAM. After bootup, I'm using about 275MB of RAM for XP
and running task. After using the computer for awhile, regardless of
program, that will increase to over 450MB with everything closed and back to
desktop. Does this sound like a memory leak, and if so, how do I identify
the program/process that is causing it?

Thanks,
Fitz

The basic principle with Windows and RAM is that "unused RAM is wasted
RAM".

Windows will, by design, always attempt to find some use, anything
whatever that might potentially be of some benefit, for every bit of
RAM installed in the computer. So it will increase the size of the
disk cache to take advantage of available RAM, and will retain the
program code from closed applications in RAM in anticipation that the
application might be launched again, as is very often the case.

And Windows will instantaneously drop the more trivial of these usages
should some better use come along for some of that RAM.

Also there are many system components and shared .DLL files that are
not loaded into RAM until the first time they are actually needed.
And because these are common items, used by more than one application
program and/or Windows function, these items will be retained in RAM
once loaded, even though the application that originally needed them
has since been closed.

Hope this explains the situation.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm

 

[Ken Blake]

In

I'm running WinXP Pro. I like to know how to identify to source
of a
memory leak. I have 1GB of RAM. After bootup, I'm using about
275MB
of RAM for XP and running task. After using the computer for
awhile,
regardless of program, that will increase to over 450MB with
everything closed and back to desktop. Does this sound like a
memory
leak,

No. It sounds perfectly normal. Windows is designed to use all,
or nearly all, your RAM all the
time. If your apps don't need it, Windows will try to find
another use for it (such as using it for cache), then give it
back when the apps need it again.

Despite what some people apparently think, this is good, not bad.
Unused RAM is wasted RAM. You paid for it all, and shouldn't want
to see any of it unused and wasted.

 

[Fitz]

Thanks for the responses and the explanation.

Fitz