Avast WEBforum
Consumer Products => Avast Mac Security => Topic started by: REDACTED on November 12, 2014, 10:59:07 PM
-
Hi there,
Sometimes when I'm using Finder the com.avast.daemond process spikes up to almost 100% CPU usage. Is there something i can do to avoid this happening? If you need more information I'll be happy to provide it, but I might need some inputs on how to provide it though.
Thanks alot!
-
Same problem.
On MacBook Pro Retina SSD with Filevault....
OS X 10.9.5
-
Same problem here with %CPU running close to 100% for long periods of time.
-
Same problem here with %CPU running close to 100% for long periods of time.
I was going to uninstall Avast and move to Sophos Antivirus for Mac when I thought that I would investigate a little bit further and determined that %CPU was the highest when I was navigating files on an external 4.0 TB drive.
To fix this and reduce %CPU from 99.0% to 0.1% I disabled File System Shield, i.e. Preferences > Shields > File System Shield -> Disable.
Interestingly, when I added the volume of my external hard drive HITACHI as an excluded path there was no difference in the %CPU, i.e. Preferences > Shields > File System Shield -> Settings -> + -> /Volumes/HITACHI.
The %CPU was only reduced to 0.1% by completely disabling the File System Shield which of course has a major drawback in not being able to successfully use this shield.
This is now the second time I have posted (https://forum.avast.com/index.php?topic=151261.msg1098861#msg1098861) this kind of problem using Avast Mac Security so I will probably move to Sophos after I update to Yosemite as it looks like Avast is not as stable running on the Mac as it is on the PC.
-
I have the same problem as the original poster. Close to 100% CPU for the daemon esp. whilst using Finder to do trivial stuff.
Starter yesterday morning. I've been running it for months with no prior issues.
None of my external drives (incl. a Time Capsule) were connected when it happened.
13" Macbook Pro Retina 3GHZ Intel Core i7
OS X 10.9.5
No Filevault.
All Avast shields enabled with default settings.
-
Moving from incorrect forum, to keep folks in the loop: https://forum.avast.com/index.php?topic=162613.0
I am having the same problem.
The process consuming CPU is: com.avast.daemon
It spawns 26 threads and holds the CPU every time i change directories in finder takes the CPU up to 95%
This is in OSX Mavericks on a MacBookPro5,3
My disk is an SSD had never have these issues before. This started happening recently, not sure if it was after the latest update to Avast.
Disabling file shield corrects the issue (but then I have no file shield :P)
-
Same problem here on 10.9.5.
This behavior started a fews days ago. Every time I want to use the finder the machine starts slowing down, I cannot even use the finder anymore.
The culprit is the avast daemon. I finally managed to disable file agent and it's now fine again.
This is really a show stopper !
-
Hello guys,
we hear you. Could anyone of you try to reproduce the issue and then (while the CPU is eaten), try to create a support package and provide it to us for analyzes?
You can find in the main GUI app, menu Help >> Avast Technical Support >> Generate Support Package.
Thanks,
Martin
-
Hi,
I just tried but it seems I cannot activate the filesystem agent. I'm getting an error : "OSStatus erreur -60007"
I managed to get around it last time by quitting avast (GUI) and starting it again but this time I have no luck.
Any hint on how to get around this error ?
Thanks
Update: I managed to restart filesystem agent by launching the Avast program from the Application folder rather than from the menu bar on the desktop ... I'm waiting for the problem to re-appear and I'll sent the support package (where should I send it ?).
-
I just tried but it seems I cannot activate the filesystem agent. I'm getting an error : "OSStatus erreur -60007"
We are aware of this issue and I am working on a fix. The workaround is to start GUI from elsewhere (e.g. Finder) and not from the helper.
The issue is that after a program update and restart of the helper program (responsible for the icon on top of the screen and pop-ups) in some OS X versions, the helper process is running in a wrong context (and it also spreads to any child process started from it). The issue persists until you log out/log in. If you then start the main GUI from it and it requires an elevation to admin rights (e.g. to change shield settings), it shall fail.
-
Hello guys,
we hear you. Could anyone of you try to reproduce the issue and then (while the CPU is eaten), try to create a support package and provide it to us for analyzes?
You can find in the main GUI app, menu Help >> Avast Technical Support >> Generate Support Package.
Thanks,
Martin
I was just experiencing this issue, and sent you the support package by private message.
-
Is this still an issue? We're evaluating a few Mac AV applications and this could sway the decision. Thanks!
-joe
-
Is this still an issue? We're evaluating a few Mac AV applications and this could sway the decision. Thanks!
-joe
If you are evaluating maybe you should try it yourself in one machine, it's free. There is a difference between a widespread issue and some people having a issue, the later being a more correct representation of this problem, as you can see only a handful of people WERE talking about it, personally I'm not currently experiencing any of the said issues.
-
This has been happening to me for over a month now. I am using 10.9.5 with FileVault on for my Macbook Pro.
I have to turn the file shield off in order to use my computer properly.
Please don't assume this isn't widespread. I notice over 1800 people have viewed this thread. My experience with users is that only a very small percentage have any idea that their computer is slowing down due to a problem- they just accept the spinning beach ball as normal. And of those that feel the problem, an even smaller percentage would ever dare run Activity Monitor to check on what is using up their CPU.
I am turning file shields back on and will send a support package.
-
Please don't assume this isn't widespread. I notice over 1800 people have viewed this thread. My experience with users is that only a very small percentage have any idea that their computer is slowing down due to a problem-
And my experience with users is that the majority assume that every problem they have is widespread, and that they usually blame the wrong piece of software.
-
Same Problem here!!!
-
com.avast.daemon using 65 % cpu
kernel_task using 41 % cpu
(hmmm, more than 100%?)
-
(hmmm, more than 100%?)
Because you have more than one core, 200% = using 2 cores at full capacity, 400% = 4 cores, etc.
-
Same problem, as Avast is eating up my cpu. Also, the scanning stops without completing a full scan. It pauses at a certain file, and never moves past it, all the while the clock keeps running.
-
I just turned off the 'File System Shield' and restarted my computer - Voila! My system is now using 3%. A drop from 96%. Unless Avast can fix this problem, I will be going to another anti-virus program. Also, Avast is still not running proper scans (it pauses on certain files and does not start up again, though the clock keeps running).
-
There was a serious bug that caused the scan engine to deadlock
on some special files in 10.6. Version 10.7 (43713) fixed this.
-
Now that we know which version of the program fixes the bug, do we know which program version numbers were affected by this bug?
-
Now that we know which version of the program fixes the bug, do we know which program version numbers were affected by this bug?
Affected versions are 10.5 (beta) and 10.6.
-
Now that we know which version of the program fixes the bug, do we know which program version numbers were affected by this bug?
Affected versions are 10.5 (beta) and 10.6.
From our experience, the bug does not seem to affect OS X 10.10 Yosemite, only Mavericks and earlier.
-
From our experience, the bug does not seem to affect OS X 10.10 Yosemite, only Mavericks and earlier.
It affects Avast on any OS X version. In your "test set" you most probably do not have 10.10 machines with
files triggering the bug.
-
From our experience, the bug does not seem to affect OS X 10.10 Yosemite, only Mavericks and earlier.
It affects Avast on any OS X version. In your "test set" you most probably do not have 10.10 machines with
files triggering the bug.
That is completely plausible since we don't have Yosemite widely deployed yet, maybe 10 clients out of 4,000.
-
I'm running OSX 10.9.5 and Avast 10.9 and am having the same issue when changing folders via Finder. Every folder change spikes com.avast.daemon process to around 100%. I'll send a test support package.
-
Avast should seriously consider adding an option, to do file scans only when plugged in to power supply.
I don't mind avast crunching through eating up extra CPU, but when unplugged, it's draining my battery like crazy. When avast file scan is active, although it does not eat 100-400% of cpu like others report (only aroung 30-50%), but my battery gets drained with in 2-3 hours, when avast file scan is off, i can get solid 6-8 hours out of my battery.
-
Avast should seriously consider adding an option, to do file scans only when plugged in to power supply.
That's a perplexing proposal, what's the point of having an AV if it's not scanning?