This user is having high cpu usage with those proccesses. The computer is a Mac using OSX 10.7.
This is after reinstalling the ePo agent and the antivirus.
Thanks.Message was edited by: demersd on 03/08/12 2:04:20 CDT PM
Is the High CPU usage happening always or in specific scenario/specific time?
It could be a DAT update during which the scanners are initialized again or it could some IO intensive task happening which is resulting in scanners working over-time.
By default you would see 3 VShieldScanner processes which serve the OAS functionality.
Additional Scanner processes can be seen for each ODS task.
You dont have to re-install the product in order to resolve this kind of issue.
Enabling the product debug logging (KB70802) would help in finding out what could be going on at that moment.
I have been suffering as similar problem but in my case the number VShieldScanner scanner processes just keeps growing. It gets to roughly 1400 instances in the activity Viewer (or `ps -ax` list) over roughly a 24 hour period then my machine hangs and I can't open anything else (not even another Chrome tab to google abbout it) The only thing I can do is restart the machine.
Me too - after rebooting, the processes continue to grow, with few, if any ending, as the oldest date back to a few minutes after the box was rebooted.
The log is filled with entries like:
Mar 23 12:07:44 macbook McAfee: : Info: LogTime: 2018-Mar-23 12:07:44 AVAS: PID: 107 : Too many scan requests pending. /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist is not scanned
Mar 23 12:07:44 macbook McAfee: : Info: LogTime: 2018-Mar-23 12:07:44 AVAS: PID: 107 : Too many scan requests pending. /Library/Preferences/SystemConfiguration/preferences.plist is not scanned
Eventually mac runs out of ram, reboot, and process starts again...
I'm seeing exactly the same thing.
: Info: LogTime: 2018-Mar-27 11:39:24 AVAS: PID: 104 : Too many scan requests pending. /System/Library/Frameworks/CoreTelephony.framework/Support/CommCenter is not scanned
These entries are flooding the logs.
Same. I've taken to manually running killall on them whenever I start to get bogged down, every few hours or so, when the number of VShieldScanner processess is around 100, just so I can keep working. Here's the command if anybody wants it for running in the terminal:
sudo killall -v -9 VShieldScanner
I have the same problem of hundreds of VShieldScanner processes starting over time until all memory is used up.
I created a crontab entry that kills them as user root:
0 * * * * pkill -f /usr/local/McAfee/AntiMalware/VShieldScanner
@Former Member: There must be a better solution, which one? What is the cause of the problem?