1 of 1 people found this helpful
I haven't seen the memory leak issue but I have seen scanningprocess.exe run more than once per cpu.
I have a quad core in my desktop and noticed 4 instances of scanningprocess.exe each using over 80MB of RAM !!. It seems it was running once for each core not once for cpu.
I found a post (link below) which helped me fix the issue. I created the reg dword as suggested with value as 1 and it worked after a re-boot. When I checked there was only one instance of scanningprocess.exe
Might help ....
Thank you I'll try that. Right now I have three ScanningProcess.exe's on my two-processor system... two owned by system and one owned by me.
Is that working as designed? Or do I need to push out the reg hack?
I've had complaints of ScanningProcess slowing down machines (including one of my machines). The one common thing I've found between all of these machines is that they were all 8.8 or 8.8 SP1 who had SP2 applied to them. On all of these machines, if I reinstall the entire agent (no uninstall first) it seems to fix the issue and no more compaints of systems running slow.
Do you physically have 2 cpu's or just two cores?
As far as I am aware by design it will run scanningprocess.exe per core not per cpu (socket) (someone please correct me I am wrong). So if you have a dualcore processor is should show scanningprocess.exe running twice in task manager.
After some testing with some newer dualcores we had here I decided to create a package for the reg change and push this out to those machines. Please note that the key location sits in a different spots between vista and xp in the registry.