Thanks for the link. I found a few other mentions on the subject as well.
I found some code (VB) to reduce the Working Set to a minimum number as is
done when the app is minimized. I'm not real comfortable with it since this
writes out to the hard drive virtual mem to clear the memory but may put it
in as a flagged function if the WS reaches a large number during runtime.
Code:
Private Declare Auto Function SetProcessWorkingSetSize Lib "kernel32.dll"
(ByVal hProcess As IntPtr, _
ByVal dwMinimumWorkingSetSize As Int32,ByVal dwMaximumWorkingSetSize As
Int32) As Int32
Public Function SaveMemory() As Int32
Return _
SetProcessWorkingSetSize(Diagnostics.Process.GetCu rrentProcess.Handle, -1, -
1)
End Function
End Function
Thanks again!
"Cor Ligthert" <no**********@planet.nl> wrote in message
news:O4**************@TK2MSFTNGP10.phx.gbl...
Gene,
What you describe seems to me the wished behaviour from the managed code.
It frees memory when it is needed or when there is idle time and it let it
stay when there is enough memory. Result is that the processing goes on and the
computer is not spending time with useless cleaning.
However when you have real memory leaking. (It is never set to lower) than
you can look to this what Rich was feeding back to the newsgroup last
week.
Before his investigation I had never heard of that problem.
http://www.google.com/gr************...TNGP12.phx.gbl
I hope this helps?
Cor