ending a process frees up more ram than the process was taking?
 

I had a process that had a Mem Usage of 685,520 K and PF usage of 2.06
GB. I end the process and my PF usage drops to 1.17 GB. That's a
~890,000 K difference - not ~685,000 K.

My question is... why the difference? Why does ending this process
free more RAM than the process was taking up? Is this what's known as
a memory leak?

ending a process frees up more ram than the process was taking?
 

yawnmoth wrote:
I had a process that had a Mem Usage of 685,520 K and PF usage of
2.06 GB. I end the process and my PF usage drops to 1.17 GB.
That's a ~890,000 K difference - not ~685,000 K.

My question is... why the difference? Why does ending this process
free more RAM than the process was taking up? Is this what's known
as a memory leak?

Why do you think that said process had no child processes that ended when it
did?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

ending a process frees up more ram than the process was taking?
 

On Feb 15, 5:45*pm, "Shenan Stanley" wrote:
yawnmoth wrote:
I had a process that had a Mem Usage of 685,520 K and PF usage of
2.06 GB. *I end the process and my PF usage drops to 1.17 GB.
That's a ~890,000 K difference - not ~685,000 K.

My question is... *why the difference? *Why does ending this process
free more RAM than the process was taking up? *Is this what's known
as a memory leak?

Why do you think that said process had no child processes that ended when it
did?

The Processes count in the bottom left went from 91 to 90. The
process in question, incidentally, is firefox.exe. I'm not aware of
any child processes that that might spawn.