These results were obtained on a server (& citadel) machine while watching taskman.exe (specifically the Lookout.exe process). The server runs 4 server processes and 4 client processes linked to their respective server processes.
It was first noticed while testing the new Hypertrend/Symlink fix on a remote client machine while watching server cpu utilization overall. Each time I loaded a new process or reloaded a process on the client machine, the server machine lookout.exe memory usage would rise about 1/2 MByte. Further testing revealed the same issue when processes are reloaded on the server machine except, the memory usage rise is in the order of 2.5+ MBytes used by Lookout.exe each time a process is reloaded.
For example, if I "reopen" all 8 processes on the server machine, its Lookout.exe memory usage rises from ~50,508 kByte to ~79, 276 kByte. A repeat "reopen" wil cause Lookout.exe memory usage to reach ~101,540 kByte.
Unloaded processes are not releasing there memory within lookout.exe.
Side Issue: Repeated testing wil also result in improper exit of lookout.exe (When lookout exits....the task manager still has lookout.exe running, but the desktop has no sign of it). The task must then be killed before lookout wil properly restart on the desktop.
NOTE: On the local machine...even an empty process(blank control panel only) will cause the symptom when loaded/reloaded. However, an empty process restarted on a client (when no connection within that process to the server exists) will not cause the increased memory usage on the server (expected).
Message Edited by erblock on 08-24-2005 04:22 PM
