same. since like some days (could be less, dont really know since when, seems like it started with latest os x safetyupdate), using it since years too never happend
os x 10.9.5
MBP
i starts instantly at startup
drives my fan cracy and heats up macbook like hell
i just shut the process down, then everything as always
I have the same issue since this morning using the updated software version.
I had to Uninstall the avast secureline vpn to stop my cpu burn like the sun.
It seems to me a serious bug problem and i hope Avast will solve it soon.
@ Eddy , what do you mean when you say if it licensed or not? Since when unlicensed software version deliberately cause trouble to users machines? This seems very UNFAIR.
Hi,
There is a serious bug in the latest SecureLine VPN application that is causing this issue. If you do not use SecureLine (which most of you don’t), you can simply uninstall SecureLine from the SecureLine application menu. SecureLine is a separate product that has nothing to do with the antivirus, so when removed, your level of protection won’t be reduced in any way.
SecureLine is installed by default with Avast unless you uncheck the appropriate checkbox during the installation. As you are suffering this issue which is caused by SecureLine and not Avast, you have SecureLine definitely installed.
The Avast version is:
Free Avast Mac Security 2015
Version 11.9 (46174)
Viral DataBase 1642500
VPN Avast SecureLine is not active
Active agents are:
File
Email
Web
I thought of stopping the responsible operation from loading at startup, but it does not display in the list.
Here is the list the Avast agents that are loaded right after rebooting the Mac, as displayed in the terminal:
You definitely have SecureLine active and running, the “launchctl list” output is a clear proof for that. Additionally, when the
“com.avast.secureline.service” process is eating up CPU, this is another clear evidence. So the solution for you is also to uninstall
SecureLine.
The hot-fix update has been released, the SecureLine application should update itself within 3 hours. This can be speeded up by execution of the following command in a terminal:
Krahulik thank you for your message. You have been very zealous in fixing the issue.
I really appreciate the software efficiency and I will continue to use it with satisfaction.