Have been running Sophos Home on a MacBook Air for years, no issue at all. Mac has been running on High Sierra OS 10.13.6 for a good while now and there have been no changes to the OS or system. But for the past six weeks or so, I've noticed my CPU straining despite very little activity, multiple times a day. The laptop gets extremely hot and the fans go bonkers. When this happens Activity Monitor shows that the process 'SophosSXLD' is using 90+% of CPU capacity, though Sophos itself doesn't appear to be doing anything other than sitting there in the background. The only way to resolve these episodes is to force quit that process. Of course, it 'respawns' and in a little while is taking over the CPU again.
I'd really like to stop this from happening, but not sure what to try from here.
>Sophos is fully updated.
>I have already uninstalled and reinstalled Sophos, with no change
Hi T M2
Could you please suggest whether you are using Sophos Home premium or basic?
If you have a license for Sophos Home, I'd request you to open a case with Sophos home support.
Jasmin Community Support Engineer | Sophos Support Sophos Support Videos | Knowledge Base | @SophosSupport | Sign up for SMS Alerts | If a post solves your question use the 'This helped me' link
Hi Jasmin, I'm using the basic version which is why I haven't opened up a support case, thanks.
Hi Cedric LEBLOND
Our team is currently investigating the issue. The workaround available is to kill the process(this is temporary). Also, if you are using Sophos Home Premium, you can log a request here for an in-depth investigation.
is there any progress on this issue ? I've moved to release 2.2.5 of Sophos Home and still have the same sophosSXLD process consuming CPU and battery !
I'm most of the time unplugged from the power and doesn't always see that my battery has emptied because of this CPU consuming process...
Thanks for your prompt reply !
Happening here, too. MacBook Pro (15-in, 2019), MacOS Catalina 10.15.2 Beta (19C46a). Makes the machine laggy. Killing the process got rid of it, for the moment.
Hi Tom Hundt and Cedric LEBLOND
I have checked regarding this issue, and our development team is currently testing the fix. Once we have the version released with the fix, we will be updating the forums. Again, Apologies for the inconvenience.