I checked what was running under the SVCHOST and I didn’t find anything out of place, but it jumped quite a bit after the scan from around 100,000 K to around 450,000 K.
This doesn’t seem normal but I can’t find anything running out of place in it and neither could Avast or Malware Bytes, should this be something I’m worried about, my system isn’t behaving weird in anyway and this is really the only time I’ve ever noticed high memory usage from it.
I’m running Windows 7 SP1 and Avast 2014.9.0.2018 and what is running under that SVCHOST is: AudioEndpointBuilder, hidserv, Netman, PcaSvc, SysMain, TrkWks, UxSms, WdiSystemHost, Wlansvc
Did you (by any chance) do that full scan with any browser Windows open? If so, close all browsers and retest. Also, has your memory usage returned to normal after a reboot? Any chance Windows Update was active in the background while scanning? Is this a repeatable condition?
I haven’t tried to repeat it, but yeah, I did have my Firefox Browser open if that’s what you mean and yes it returned to normal after a reboot
Edit: Just ran one now, it didn’t jump as high, capping out at around 220,000 K but that still seems way higher then it should be and it only does it when Avast does a full scan, all browsers where closed and the only thing that was really running was Avast.
Sounds like those open browser windows might have accounted for some of the memory usage. I know that an open browser window will continue to use additional memory if you are parked on a website that has constantly changing (eg, rotating) banners. Also glad to hear that it returned to normal on a reboot but there still could be a possibility that something else might be accessing the internet while Avast is running so try this if you would like:
Disable internet access (wifi or ethernet) and rerun the full scan.
Yeah, I know things are accessing the internet even while the browser is closed, I just want to know if this is a flaw/virus in my system, a problem with my system or if it’s just Avast and Windows 7.
OK, I just did a full scan with internet access enabled, no browser windows open, and I experienced the same results as you. Specifically, my committed memory jumped about 400mbs and stayed there until I rebooted. Moreover, when I looked at proc mon, it showed that Avast had retained a large chunck of committed memory after the scan when it should have released that memory IMHO. Anyway, I do not believe there is anything wrong with your rig (or mine). The only difference is I am running Win 8.1. You can open a ticket with Avast at this point if you so desire. Good luck with your decision.