http://s020.radikal.ru/i710/1310/58/6460089d2a94.jpg
http://i031.radikal.ru/1310/d4/ecd121410c70.jpg
Best answer by Rakanisheu Retired
View originalBest answer by Rakanisheu Retired
View originalPlease see here as I explained about Win 8.1 x64 and the fix from Microsoft and now the issue has reappeared in Windows 10 x64 it never happened with Win 8 x64 and it's not Webroot's fault we just have to wait for a fix from Microsoft again: https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/Explorer-exe-using-up-to-300mb-RAM/m-p/198377#M15753@ wrote:
I'm having the same problem again. How is it Microsofts fault? It's their fault for certifying the Webroot program as compatible with Windows 10 when it isn't. Webroot knew about this from the windows 8.1 version and you have posted that the problem was on the windows 10 preview versions. So Webroot should have fixed by the Windows 10 release date. It's not just that explorer uses more memory. Explorer doesn't function properly either all the thumbnails have to regenerate every time you open up a folder wasting system resources. I set all my junk file cleaning programs so that they don't delete the thumbnail cache because I can't stand waiting for them to regenerate, but because of this problem I have this happens all the time. I'm sure it causes other problems too! Before I just installed the windows 8.1 update that corrected this now I have to disable Webroot and install Bitdefender until there's a fix. I am highly irritated and last time I had this problem Webroot Support was no help at all! I also remember asking if Webroot was going to have a version that works right with Windows 10 when it was ready! I'm going report this to Microsoft just for the hell of it and ask them why they certified a program than causes Windows 10 to not work right?
Definitely there is a memory leak.. because more memory is used. What actually causes is the issue here. One of the leading alternatives to Windows Explorer (aka File Manager) , Directory Opus handle the memory pretty well with WRSA running even if we set it as default file manager for windows - it takes just 20 MB.@ wrote:
It's definitely a memory bleed and not because of Webroot and explorer.exe preparing to sync files. I was hoping for best but now irritated again.https://youtu.be/uTe5VsKaPAk
@dtouch wrote:I think perhaps these two postsare the ones that
...could anyone link to@ 's previous post explaining this before. I missed it.
Reserving empty space on your hard drive? I'm not the best placed to comment but personally I'd be surprised if the above was true.@ wrote:
...your going to have to wait for your hard drive to respond which will slow up your system. So any system resource advantage to using Webroot over other antivirus software is nullified while this problem exist.
I am not sure what you have been smoking but where did you manage to dig up such an outlandish hypothesis?@ wrote:
Thanks for the expectation, but if it's a pagefile problem it's worse then if was just a ram problem. If it was just a ram problem and you have plenty of ram on your computer it' s not going to really affect your computers performance. If it's a pagefile problem and you have a regular Hard Drive and not a SSD your going to have to wait for your hard drive to respond which will slow up your system. So any system resource advantage to using Webroot over other antivirus software is nullified while this problem exist.
This would be true, if the allocation were more dynamic. And that is the reason I pointed out that there are more types of memory that reside in the page file that what you are seeing in this case.@ wrote:
Thanks for the expectation, but if it's a pagefile problem it's worse then if was just a ram problem. If it was just a ram problem and you have plenty of ram on your computer it' s not going to really affect your computers performance. If it's a pagefile problem and you have a regular Hard Drive and not a SSD your going to have to wait for your hard drive to respond which will slow up your system. So any system resource advantage to using Webroot over other antivirus software is nullified while this problem exist.
@ wrote:
With this said, WSA loads a DLL into the Explorer process. This isn't uncommon, and is a fairly frequent occurrence for system utilities. Because of this 'injection' it makes sense for Explorer to create a buffer to improve stability. Particularly during the early release stages of the OS as many of the hardening functions haven't been written to solidify the process in question.
This is EXACTLY what is taking place in this instance. Explorer is detecting our DLL load and is insolating it against crashing. It's a fault protection, and as I mentioned in my original discussion, is actually a GOOD THING to do.
Thank you.@ wrote:
@dtouch wrote:I think perhaps these two postsare the ones that
...could anyone link to@ 's previous post explaining this before. I missed it.
@ is referring to:
https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/Explorer-exe-using-up-to-300mb-RAM/m-p/117664/highlight/true#M7014
https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/Explorer-exe-using-up-to-300mb-RAM/m-p/121332/highlight/true#M7117
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.