Explorer.exe using up to 300mb RAM.

@ wrote:
Webroot SecureAnywhere AntiVirus (2014) 8.0.4.57
http://upyourpic.org/images/201312/om49atbrwa.jpg
Install 8.0.4.57

May I ask where you got that Download link from? And can you EDIT it out of your post please!
 
Thanks,
 
Daniel

So what are you trying to say? Please don't make it a mountain when it's only an ant hill.
 
Daniel 😠

@ 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.

I am not sure what you have been smoking but where did you manage to dig up such an outlandish hypothesis?

Update from JoeJ:
 
Quote:
 
"However, as I've mentioned in the other thread, the Explorer RAM issue will not affect your system performance: Explorer is using paged memory and only when it is not being requested from other processes so it will have no system performance impact, even if you only have 1GB of overall system RAM."
 
And it's still on the list and they will get to it!
 
Daniel

It doesnt matter if you have 1gb or 4gb Windows allocates 4gb of Virtual memory (VMM) for it to operate so this 300mb isnt actual RAM usage but paged memory. People are getting mixed up on how processes use allocated memory. 
 
Not to mention the fact that WSA only uses normally a few MB`s of memory when its running unlike many other AV`s that use a couple of hundred. 
 
https://en.wikipedia.org/wiki/Paging

@ wrote:
So let me make sure that I understand this situation correctly. .In order to have this fixed I already (2nd day as a webroot member) have to have a person go in my pc remotely?so no general fix through firmware update?
Every site like pcmag etc did they miss this info? I hope that it was not done on purpose to hide the foot print under explorer.exe .. I just find it weird that every single reviewer didn't mention this..maybe they haven't noticed??I am not accusing webroot, but this definitely needs to be fixed. .we need a time frame,we need an explanation. .This is totally against what is advertised..ohh webroot uses 3mb of ram blah blah blah..obviously it doesn't. .actually uses more at this point than my norton 360 2014
Was explorer.exe even designed by Microsoft to idle at 290-300 mb?What other system instability can that cost? Do we know?maybe maybe not. ..

If you read the entire thread, even just the last 6 replies, you would note that this bug does not affect all users.  Thus, PCMag missed nothing and nothing was hidden.
 
Further up in this thread a Webroot Product Manager wrote that a fix is currently in testing, hopefully to be released soon.
 
Timeframe is simply once the fix has been proven to work without causing any other problems... 

Nothing new here Mike Window 8.1 Pro x64 Update 1 on my VM.
 
Daniel
 

@ wrote:
Hello explanoit, MayI ask what causes a memory leak? You say a Third party and that means? Excuse me I'm just trying to understand what else could cause this..Java scripts, paging, I'm not that technical ...please address ...

Thanks, Sherry

   Hi @ 
 
A memory leak is simply when any program  fails to release RAM memory 'addresses' once that RAM "address" is no longer in use.  The effect of it is that the amount of RAM taken up by that program goes up and up and up...  
 
In most cases, this has a severe impact on system performance.  The RAM allocated to that program just plain will not be released back in to availability.  This of course causes a low memory available situation and slows down the device.  The slowdown is due to the fact that with no RAM memory available, the device now has to start using hard disk memory as RAM.  This is called Virtual RAM or Virtual Memory.  
 
What is curious in this situation is that what appears to be a memory leak does not affect performance.  Usually the memory tied up will just plain refuse to release at all: only a computer reboot will cause the 'stuck' RAM addresses to freed.  In this case, even though RAM portions that are no longer actually in current use by WSA are failing to be released as they should, and thus causing the huge memory usage noted in this thread, once other processes are asking for more memory it does allow those portions to be used.  That is why there is no system performance hit.  The RAM does release if there is a request for more memory.
 
This bug only seems to affect certain users.  In this case, I THINK it is certain versions of 64 bit Windows.
 
Pretty confusing I know, and I am not sure I explained it quite correctly.  @  can you take a look and provide your insight?

@ wrote:

Where is the update and bug fix?

Hello ZockerFreak,
Welcome to the Community!
 
What do mean? There was no official information on this matter.
I'm sure Shawn will let us know when TechSupport officially considers this issue to be resolved.
 
Regards,
 
Mike
 
 

@DavidP1970 wrote:
Well, we do know that the isssue is being addressed, but we do not know an ETA for the fix.  That is normal, there usually is not an exact estimate until the fix is ready.  
 
Apparently, from what most people have said, it actually is not causing a significant problem with system performance.

That is very true David.  It only seems to be affecting a small minority of users...which is unfortunate.

Well we will Ping @ to see if he can give us an update from this post: https://community.webroot.com/t5/Webroot-SecureAnywhere-Antivirus/Explorer-exe-using-up-to-300mb-RAM/m-p/100382#M6189
 
Daniel

Your question has been answered on previous pages a number of times. Its a bit of big thread but worth a read if your interested.