Possible bug: Avast home build 4.6.744 and Folding@home

Hi all, just registered to post a possible bug in the new build of avast.

I have the Folding@Home 5.03 client running on my computer all the time. Yesterday when I got back home, the computer was nearly frozen. I Ctrl+Alt+Delete 'd and saw that ashServ.exe was taking up 99% CPU time instead of the usual F@H taking up all the available time.

Now, since ashServ needs High Priority to work nicely, you can imagine that the computer was totally unusable. Slowly and painfully I stopped all running avast! agents, to no avail. I killed the ashServ process only to find out that the resident protection would now not start. I rebooted a couple of times without any change in behaviour. Only when I deleted the F@H link in the startup folder ashServ was happy once more.

At last, I had to tell avast!'s standard shield to not check inside the folder of F@H and everything is OK. I post this however as it might be a problem with any other process utilizing 99% CPU.

Thanks for a great anti-virus software,

Alex

I won’t call it bug but a driver conflict or a trouble into any F@H file…
Can you check into Standard Shield settings (or Internet Mail provider) which is the last filed scanned?

Sounds rather strange. Wasn’t VRDB generation in progress when you came to the computer? I really don’t think avast! has any problems with CPU intensive applications.