I've been seeing Webroot's wsdaemon process taking up 90% of my RAM (7.27 of 8GB), after which it starts to cause issues with other applications, e.g. that Chrome will show 'the connection has been reset' for various websites. After I kill wsdaemon in the activity manager, things operate normally. I have had to do this multiple times after doing a clean install of MacOS Catalina. I reinstalled the OS from scratch, i.e. a clean install. I've also kept the OS and Webroot SecureAnywhere up to date. The scan log doesn't show any errors. Any thoughts? It seems like a memory leak to me.
Best answer by ProTruckDriverView original
was this resolved? I have the same issue; it takes 27GB RAM!!
If you have still not heard from support, please send me a private message with the e-mail attached to your webroot account. I can look into your ticket once I have that info.
Support usually takes 24 to 48 hours. There might be a slight delay due to COVID 19 since they are working from home. I’ll ping
@khumphrey our Community Specialist to see where your Support Ticket is in the queue.
Thanks for the reply,
@hungpham. I don’t have Dropbox nor Google Drive installed. Of course, there are other processes running, like Spotlight and backupd, but nothing else that I can tell in top or Activity Monitor that’s a real issue.
Rather, I noticed just now that the size of the wsdaemon grows over time. Initially, it's 97.7 MB (I saw that now after I killed the process in Activity Monitor). When I killed it just now, it was 3.7GB; I think if I left it, it would kept growing to fill up all available memory (a couple days ago, it was at 7.2GB when I killed it; I have 8GB on my system).
I also just checked off the option ‘Reduce resource use when intensive applications or games are detected’ to see if that helps.
I haven’t heard back from support yet. How long does it usually take? I submitted my request online, via https://www.webrootanywhere.com/servicetalk.asp.
Check if you have Dropbox or Google Drive installed and activated. It will take loooooong time and use much RAM.
Thanks. I did submit a support ticket in parallel to creating this topic; I was just hoping someone on the forum may have seen this behavior while I wait for Webroot Support to get back to me. I’ll also post an update when I get a response back from support.
@burvil , Welcome to the Webroot Community Forum.
Please submit a Support Ticket or Contact Webroot Support to sort this problem. This service is FREE with a Paid Subscription. When sending in a Support Ticket a Webroot Log will automatically be sent with the Support Ticket for Webroot Support to look over and see what the problem is.
Support Ticket System is Open 24/7
Note: When submitting a Support Ticket, Please wait for a response from Support. Putting in another Support Ticket on this problem before Support responses will put your first Support Ticket at the end of the queue.