Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: solek on September 01, 2020, 06:16:44 PM
-
After upgrading avast antivirus version 20.7.2425 (сборка 20.7.5568.590) RAM usage increased to 86%/12GB of 16GB RAM, before last update RAM usage was 3 GB/20%.
My system - Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1
How the fix this problem ???
-
Reboot 2-3 times. That helped me.
-
Hello, I have the same problem with Windows 10 Pro and last Avast update today. I'm writing fast before next freeze.
There is a memory leak which go to 100% use of my 8Go of RAM, then PC become incredibly slow. I tried to wait, but after some time, like 10-15 minutes windows crash then reboot.
Tried to reboot few times too but that didn't help. I want to try uninstall it but fear that could make more damage somehow since we don't know the exact origin of the problem.
-
Windows 10 Pro, 32 GB RAM. Avast was consuming all the RAM and was still increasing the pagefile immensely. So I uninstalled it. I will reinstall it later to see if the problem persists.
-
Which process was using the memory? Would you be able to make a dump of that process?
-
I'm also experiencing memory leaks today. I also updated avast today. Never had a memory leak in my life before.
I believe it is caused by avast. I installed poolmon.exe (Windows Dev Kit and all that) and I'm sorting the tables by the difference of allocations and frees. The tags named CM44 and CMpb for me have the highest values.
I went into Windows/System32/Drivers and used the command "findstr /s CM44 *.*" (and for CMpb). I'm getting a lot of things like:
FINDSTR: Cannot open Avast\2057\avast.vc140.crt\api-ms-win-crt-private-l1-1-0.dll
And many more. So I think the leaks are caused by avast. I'm not an expert though, as I've never had memory leaks before. I'm following this post as a guide:
https://superuser.com/questions/949244/windows-10-high-memory-usage-unknown-reason
Anyway, now I'm going to uninstall avast. For whatever reason, Google Chrome says that the avastclear.exe which I downloaded from https://www.avast.com/uninstall-utility cannot be downloaded securely. I scanned avastclear.exe with avast and it says no problems were found *sigh*.
I would post screenshots but drag&drop didn't work :P
-
I experienced the same problem after updating Avast to the new version. CPU was above 50%, 8Go of Ram were at 97%, the SSD was at 100%, and even the GPU was at 20-30%, and all those things without anything open. Obviously, i saw the problem after my PC froze a first time and i had to shut it down manually. (My PC is Windows 10 by the way.)
Thanks to Zemo post above, it conviced me to do the same, by following the process to uninstalling Avast and reinstalling it.
After reinstalling Avast, i restarted my computer (I'm cautious^^), and thus far, it work normally, with CPU at 1-5% and Ram at 30% when nothing is open, which is my normal as far as i know of it.
For today, i shall consider the problem fixed thanks to clean unistall/reinstall of Avast.
-
I uninstalled avast. Those CM44 and CMpb things are gone from poolmon.exe. It seems like there are no memory leaks so far, but since Windows 10 full of bloatware, I can't really tell at a first glance. My current memory usage is 5.3GB but I think that's normal for Windows 10. Before uninstalling avast, the memory usage would steadily climb to 15.95GB (99% memory) in about an hour.
I've been using avast for about 20 years and never had an issue like this before. I'm temporarily keeping avast from my computer until you confirm fixing this issue.
I attached some screenshots of poolmon and findstr and taskmgr. Poolmon screenshot is sorted by the difference of allocations/frees descending.
-
I experienced the same problem after updating Avast to the new version. CPU was above 50%, 8Go of Ram were at 97%, the SSD was at 100%, and even the GPU was at 20-30%, and all those things without anything open. Obviously, i saw the problem after my PC froze a first time and i had to shut it down manually.
Thinkpad E560, Win10 build 2004 ver. 10.0.19041.450, fully updated, 16 GB memory.
I had the same problem with build 20.7.5568. Bad actors: afwServ.exe (24 - 25% CPU, vs. 0.07% average for build 20.6.5495), and AvastSvc.exe (24 - 25% CPU vs. 0.77% average). CPU usage figures are at system idle. The memory leak (deluge?) makes sense - black screen after about 30 minutes light use.
I've reverted to build 20.6.5495 until this foolishness ends.
-
Also have had the same problem. My PC works for about 30 mins while idle and have watched the memory usage increase until the PC hard locks and I have to press the reset button. Have currently uninstalled Avast until this is hopefully fixed..
-
Hi guys, if you're willing to help, see: https://forum.avast.com/index.php?topic=237567.0
-
Finally, I choose to uninstall it yersterday evening. Like others the problem stopped after that.
I took Avast on official website and reinstalled it one hour ago, for the moment I don't see anything wrong in performances. Though there is now 6 avast processus : 4 "Avast antivirus", 1 "Avast Software Analyser" and 1 "Avast remediation exe". I don't think I ever saw this last one before by the way. It's some kind of diagnosis tool I suppose ?
Asyn, I can't help with what you asked since the problem don't reappear obviously. I will keep Avast for few more hours to see if that happend again.
Though after that I will uninstall it again and go for native Windows AV + Malwarebytes occasionals checks for the time being. Even if everything seem to work fine now, I don't really like having a possible threat looming over, so I will just wait and check sometimes here in near future to see if the bug has been identified and resolved.
-
Asyn, I can't help with what you asked since the problem don't reappear obviously. I will keep Avast for few more hours to see if that happend again.
NP, if a reinstall fixes it, it's probably "just" an issue with the update process.
Anyway, that would be something for the devs to investigate/answer/confirm.
-
Hi guys, we unfortunately can't reproduce the same issue here in Avast.
Could you please confirm that you also see the huge memory allocation in Task Manager (tab Performance -> Memory) for "non-paged poll" (as mentioned by slowui). If so, please provide us the the complete txt output from poolmon utility (poolmon.exe -u -n poolmon-log.txt) or if screenshot, then please sorted by bytes (poolmon.exe -u).
Or if even better would be the manually initiated full memory dump from the affected OS (e.g. https://docs.microsoft.com/en-us/windows/client-management/generate-kernel-or-complete-crash-dump)
Thank you.
-
One more question to you guys, who have the problem: can you specify your Avast version? Free or Premium? Thanks!
-
I'm back to previous version (used the windows restore point) so can't reproduce the problem again to take screen shot.
Anyway one of the Avast processes (started by SYSTEM) was constantly at 13% CPU or higher.
Memory consumption kept getting toward 100% until it was impossible to do anything on PC and system had to be rebooted using button.
System is Windows 7 Ultimate 64 SP1.
Avast is free version and this is the first time I have problem with it, after using it for more then 10 years.
I really want to keep Avast at least while I am still using Windows (planing to switch to Linux eventually since I refuse to get win 10), so going to wait until this version is fixed or next one is released before trying to update again.
-
Long time Avast Free user here. The latest program update made my system too unstable that I had to uninstall it and then do a fresh install.
- After immediate program update Reboot, my system hanged. Had to restart using the casing Restart button.
- Total CPU usage was at constant 25% at idle.
- Out of my 4 CPU cores, 3 cores-usage was at single digit % and only 1 core-usage was at double digit %.
- My 8GB RAM-usage was at around 50% at idle.
I would provide more help but unfortunately(fortunately) I'm not experiencing any negative issues after the fresh install.
EDIT: This is how it is now:
(https://i.imgur.com/6ubcagS.png)
-
I'm not sure if it is related to this but since the Avast Update yesterday i had Blue Screen Crashes every 30-60 minutes
running Windows 7 SP1 and Avast Premium Security
On 2 other computers in our household running Windows 10, there were no issues i know of until now.
The error in the Blue Screen message was most of the time irql_not_less_or_equal.
Every hardware test succeeded without errors.
The only thing that stopped the blue screens was a complete deinstallation of Avast.
Repairing or disabling some or all of the modules did not help.
-
Hi ryo-ken-ohki, could you please share with us the memory dump file, which had been created during the BSOD. Please look in the folder c:\Windows\Minidump (and search for the newest file available there) or file C:\Windows\memory.dmp. Thank you.
-
i sent the dumps through the contact page since the forum does not allow dump files also not zip files as attachments.
-
I use Avast free antivirus 20.7.2425 (сборка 20.7.5568.590)
Photo from Task manager
https://failiem.lv/u/9utjsvd2#/view/samrnugw
https://failiem.lv/u/66844kc5#/view/f6mvwqtm
c:\Windows\Minidump Dump file
https://failiem.lv/f/h4z7g9m9 (https://failiem.lv/f/h4z7g9m9)
-
Not seeing this on my Win10 Laptop with Avast Free 10.7.2425 (build 20.7.5568.590) UI-1.0.552, CPU and RAM usage relatively small.
-
Thank God for this thead.
Same thing happened to me, CM44/CMpb kept growing in the memory pool for me until it occupies 100% and the whole PC froze. I was using Avast Premium Security.
Repair didn't work but uninstall and a clean download/install seems to have eliminated the issue (so far)
-
Using Avast Free 20.7.2425 (build 20.7.5568.590)
Using Windows 10 64 bit.
and I updated it today and I have had my system just lock up twice now since I updated it. Never had issues like this before. Obviously a serious issue that needs to be fixed now.
Odd why Avast is using 32% or more of my CPU.
I had updated the version and also uninstall and reinstalled it and does not seem to fix the problem.
-
Does resetting Avast settings (Settings => General => Troubleshooting => RESET TO DEFAULT) make any change?
-
So I rolled back my windows system restore and my numbers are once again normal for Avast with CPU usage. No more lock ups.
I would say this is an issue that needs to be looked at as a CRITICAL issue Monday morning with a fast turn around resolution. Why are there also more Avast things added to TaskManager in the latest update?
Either way, this update should be pulled and not be allowed to destroy peoples machines.
Please see the attached image after rollback.
Can you let us know when this issue is resolved.
-
Any news on this issue yet Avast? Is anyone looking into this problem?
-
We have localized one issue which might be related to this, but for confirmation we would need output from poolmon tool from some of the affected machine. The fix is going to release soon.
-
Memory leak on CM44 and CMpb on poolmon.exe
Windows 10 pro 19041.508
Avast Premium Security v20.7.2425
On BDOS screen said: "ASWNETHub.sys" (On drivers folder)
log of poolmon.exe (with poolmon.exe -u -n poolmon-log.txt)
https://puu.sh/GqHdr/1020f956c1.txt
-
I have been having the memory leak problem for several weeks, and have just today tracked it down to an AVAST routine.
I did not have poolmon.exe on my system, but did find a program called poolmonx.exe which I have installed. It gives me a GUI look at what is going on. I sort on memory size and have four tags (fwLP, fwRN, fwRC and KLbp) that quickly rise to the top. All have non-paged memory steadily rising. In order to keep the computer from freezing, I have entered a task in the task scheduler to restart every 12 hours. In those 12 hours, the memory usage slowly climbs from 2.0 Gbyte to 5 or 6 Gbyte, with the growth being in the non-paged memory and with those four tags adding up to most of that.
I will try the uninstall and reinstall to see if that cures the problem.
I do not seem to be able to copy the output of poolmonx and so cannot post that here.
At the moment there are 1.6 Gbyte of non-paged pool memory. The amount of Kbytes for those four tags is 616021, 358138, 238754, and 70907 respectively. That adds up to 1,283,830 Kbytes or 1.22 Gbytes. Hence those four tags, all associated with aswNETHUB.sys, account for a large portion of the excess non-paged pool memory.
-
I will try the uninstall and reinstall to see if that cures the problem.
I tried to uninstall and Avast gave me an option to "repair", which I did. That did not fix the problem.
It also warned that an uninstall would get rid of things I want to keep, e.g. saved passwords. Is there a way to save passwords before uninstalling?
-
I have Avast Free 20.7.2425 running on 9 incarnations of Windows x64 (7, 8.1, 10-1909 and 10-2004), either installed as a version update or using the offline installer. Also installed are OSArmor 1.4.3 and Malwarebytes Anti-Exploit 1.13.1.254. From the number of reports of memory management problems, I am surprised that at least one of mine is not affected.
-
Hi dale5351, thank you for provided pool tags. We are looking for the cause of your problem and we will release an update ASAP.
-
On one of the forum threads it was suggested to install the latest beta, which I did. I still have the leak. After last reboot about 10 hours ago, my non paged ram is at 1.8 Gbyte, from a start of 200 Mbyte. The tags with the highest amount are fwLP, fwRN, fwRC and KL6P accounting for 1.36 of the 1.8. Other tags in the top ten are ismc, Nr22, and ArL2.
Is there a way to completely uninstall avast but keep the saved passwords and other settings so that they are there when I reinstall?
-
On one of the forum threads it was suggested to install the latest beta, which I did. I still have the leak. After last reboot about 10 hours ago, my non paged ram is at 1.8 Gbyte, from a start of 200 Mbyte. The tags with the highest amount are fwLP, fwRN, fwRC and KL6P accounting for 1.36 of the 1.8. Other tags in the top ten are ismc, Nr22, and ArL2.
Is there a way to completely uninstall avast but keep the saved passwords and other settings so that they are there when I reinstall?
Hi,
If you are referring to Avast Passwords data, then you can export to file.
If only the passwords for Avast Passwords, then you can export to Google Chrome, FireFox.
Please see this guide: https://support.avast.com/en-ww/article/Export-Google-Chrome-Passwords-data/
-
Whats the update on this fix for the memory leak? Its been a bit now.
-
Looking for an update on this as well. I have the same issue and my PC has been almost unusable for 2 days now.
-
Whats the update on this fix for the memory leak? Its been a bit now.
-> https://forum.avast.com/index.php?topic=238264.msg1562219#msg1562219
-
If you are referring to Avast Passwords data, then you can export to file.
If only the passwords for Avast Passwords, then you can export to Google Chrome, FireFox.
Please see this guide: https://support.avast.com/en-ww/article/Export-Google-Chrome-Passwords-data/
That does not work for me. I open the passwords page and all I get is an icon asking me to upgrade.
-
Whats the update on this fix for the memory leak? Its been a bit now.
-> https://forum.avast.com/index.php?topic=238264.msg1562219#msg1562219
I have installed beta (20.8.2428, build 20.8.5646.561) and am still having the same memory leak. Tags with high non-paged memory usage remain the same.
-
I had the same issue , i could not figure out for the life of me what was causing my memory to spike and i have 32gig , this is the first issue I have ever had with my new pc build but i finally stumbled onto this and it hit me that i have not had any issues at all until i installed the avast cleanup but i decided to uninstall avast ( I have the paid version) and the issue has since went away , so Im about 90 percent sure that avast was causing my memory leak issue
-
Hi dale5351,
Unfortunately, we are not able to reproduce your problem or find a scenario for how it might arise. Please, could you send us internal network driver log? Don't worry, the log is encrypted and for decoding, you need a special file accessible only to us in Avast. Here is simple guide how to do it:
1) Reboot computer and open command line in the administrator mode
2) Download and change extension of both attached files to the .bat
3) Turn on logger by the ManualLogger-Verb-Start.bat
4) Let the computer run for a while to allow memory leaks to accumulate
5) Turn off logger by the ManualLogger-Stop.bat
Folder \Windows\System32\LogFiles\WMI should contain the file aswNetHub.etl or simmilar.
Please, send us this file.
Thank you very much in advance
-
Whats the update on this fix for the memory leak? Its been a bit now.
-> https://forum.avast.com/index.php?topic=238264.msg1562219#msg1562219
Is there an estimate on when this beta will be released normally? I have also been having memory/CPU issues with the current version of Avast (it's constantly been using ~2GB of RAM and slowing down all other programs), but I cannot uninstall it so I've been waiting for a way to update to a fixed version.
-
Hi dale5351,
Unfortunately, we are not able to reproduce your problem or find a scenario for how it might arise. Please, could you send us internal network driver log? Don't worry, the log is encrypted and for decoding, you need a special file accessible only to us in Avast. Here is simple guide how to do it:
1) Reboot computer and open command line in the administrator mode
2) Download and change extension of both attached files to the .bat
3) Turn on logger by the ManualLogger-Verb-Start.bat
4) Let the computer run for a while to allow memory leaks to accumulate
5) Turn off logger by the ManualLogger-Stop.bat
Folder \Windows\System32\LogFiles\WMI should contain the file aswNetHub.etl or simmilar.
Please, send us this file.
Thank you very much in advance
Here you go -- two file attached. First a screen shot, second the log file.
-
Log file would not send. File too large. Can you send me an email address to send via attachment? Or some other way to get it to you?
Thanks for efforts.
-
After reboot, I ran the monitor for shorter period of time. This time the file is less than 1 Meg .
The system would not allow me to upload the *.etl file. I renamed it to *.txt and hope that can work for you. Otherwise -- give me more explicit info as to how to get it to you.
-
Log file would not send. File too large. Can you send me an email address to send via attachment? Or some other way to get it to you?
Thanks for efforts.
You can upload your file(s) here: ftp://ftp.avast.com/incoming/ (ftp://ftp.avast.com/incoming/)
Pick a unique name (and post it here), so the devs can find it. Thanks
-
Whats the update on this fix for the memory leak? Its been a bit now.
-> https://forum.avast.com/index.php?topic=238264.msg1562219#msg1562219
Is there an estimate on when this beta will be released normally? I have also been having memory/CPU issues with the current version of Avast (it's constantly been using ~2GB of RAM and slowing down all other programs), but I cannot uninstall it so I've been waiting for a way to update to a fixed version.
Update to the latest version (20.8.2429): https://forum.avast.com/index.php?topic=238421.0
-
You can upload your file(s) here: ftp://ftp.avast.com/incoming/ (ftp://ftp.avast.com/incoming/)
Pick a unique name (and post it here), so the devs can find it. Thanks
I clicked on that link, but am not certain how I can place a file there. I tried to do a drag and drop, but did not see it appear there. Just in case it did work:
name of file = aswNetHub_from_dale5351.etl
Also, I do not think that I have said that this computer is using win 10 home, wireless connection.
-
You can upload your file(s) here: ftp://ftp.avast.com/incoming/ (ftp://ftp.avast.com/incoming/)
Pick a unique name (and post it here), so the devs can find it. Thanks
I clicked on that link, but am not certain how I can place a file there. I tried to do a drag and drop, but did not see it appear there. Just in case it did work:
name of file = aswNetHub_from_dale5351.etl
Also, I do not think that I have said that this computer is using win 10 home, wireless connection.
Update to the latest version that was just released and addresses the problem.
Details https://forum.avast.com/index.php?topic=238421.0
-
I installed 20.8.2429 Yesterday. I am still having the memory loss problem due to non-paged memory growth from Avast routines. Now what?
-
Hi dale5351 and thank you very much for cooperation. Unfortunately larger etl file didn't arrive and shorter one is corrupted, maybe because of text conversion. But due to problematic memory tags it looks as one system callback in our driver is not working on your system. It could be some kind of conflict with another software using the same API. Do you have some network filtering/monitoring software installed? Maybe some another antivirus, network monitor or firewall?
Regarding the larger etl file I will send you private message how to do it.
-
Hi,
I have same issue here.
Only Windows 10 (1909 and 2004) security tool and avast.
If no internet, no ethernet cable connect, all is normal.
Soon ethernet cable is connected, avast memory leak starts, not stop, use all ram and swap.
Memory leak occur when try to open UI or if UI are open.
The problem happens on previous version of avast and last update (30 Sep 2020).
-
Whats the update on this fix for the memory leak? Its been a bit now.
-> https://forum.avast.com/index.php?topic=238264.msg1562219#msg1562219
Is there an estimate on when this beta will be released normally? I have also been having memory/CPU issues with the current version of Avast (it's constantly been using ~2GB of RAM and slowing down all other programs), but I cannot uninstall it so I've been waiting for a way to update to a fixed version.
Update to the latest version (20.8.2429): https://forum.avast.com/index.php?topic=238421.0
Thank you! I updated to the version released yesterday which partially fixed the problem (RAM usage went down to ~1GB), but the October update seems to have fixed it completely now. :)
-
Hi dale5351 But due to problematic memory tags it looks as one system callback in our driver is not working on your system. It could be some kind of conflict with another software using the same API. Do you have some network filtering/monitoring software installed? Maybe some another antivirus, network monitor or firewall?
Only windows defender, and I am not sure if it is active.
Regarding the larger etl file I will send you private message how to do it.
Will do as soon as I close this post. Thanks for keeping with me on trying to solve this problem.
-
Whats the update on this fix for the memory leak? Its been a bit now.
-> https://forum.avast.com/index.php?topic=238264.msg1562219#msg1562219
Is there an estimate on when this beta will be released normally? I have also been having memory/CPU issues with the current version of Avast (it's constantly been using ~2GB of RAM and slowing down all other programs), but I cannot uninstall it so I've been waiting for a way to update to a fixed version.
Update to the latest version (20.8.2429): https://forum.avast.com/index.php?topic=238421.0
Thank you! I updated to the version released yesterday which partially fixed the problem (RAM usage went down to ~1GB), but the October update seems to have fixed it completely now. :)
You're welcome.
-
Hi Dale5351,
thank you for provided etl log. It successfully arrived and it is full of mDNS packets. I'am not sure for 100% but these mDNS packets probably cause your problem. I found there many mDNS connections that the system never closed.
I would prepare some simple test how to verify my suspicion. Or, If you are familiar with some firewall (Avast, windows defender etc.) you could try to set rule blocking all UDP packets from/to remote port 5353.
-
Hi,
I found another system with memory eating avast installation.
Windows 7, 7601 SP1 on Intel G645, 4GB of ram
Avast version: 20.7.2425 Build 20.7.5568.598
Huge memory start soon after network/internet connection are established.
edit:
Update avast to version 20.8.2429 build 20.8.5653.56
and problem persist.
edit2:
AVG is in same situation.
-
Dear Avast Team,
I also have the same problem and I am not going to repeat what other users have described again.
It seems that the usage problem happens among a large group of Avast users and uninstalling Avast to 'save the computer' is quite common, would Avast Team please make an announcement on top after your have solved the problems, so that users will know when to re-install Avast again?
My computer freezes during the process and I have to directly turn my computer off, which may in turn harm the PC. Therefore, I hope that before reinstalling avast again, at least users could know the problem has been solved.
Please consider my suggestion. Thanks
-
Dear Avast Team,
I also have the same problem and I am not going to repeat what other users have described again.
It seems that the usage problem happens among a large group of Avast users and uninstalling Avast to 'save the computer' is quite common, would Avast Team please make an announcement on top after your have solved the problems, so that users will know when to re-install Avast again?
My computer freezes during the process and I have to directly turn my computer off, which may in turn harm the PC. Therefore, I hope that before reinstalling avast again, at least users could know the problem has been solved.
Please consider my suggestion. Thanks
Have you updasted to the latest version just released, I states that it has addressed this problem.
https://forum.avast.com/index.php?topic=238421.0
-
I am sorry, I put the comments on the wrong thread. My PC was fine with Avast ver 20.7.XXXX. Actually I am referring to the computer crash/High CPU usage problems with 20.8.XXXX, i.e. the issue described in the following thread
https://forum.avast.com/index.php?topic=238442.0
It seems some other threads are discussing the CPU usage problems. That's the reason why I suggest Avast make an announcement on top if the issues are fixed - If they just give an announcement under one thread, users may not know if they only read the other threads and can't realize the problems are solved and hence re-installed Avast again
-
Hi Dale5351,
thank you for provided etl log. It successfully arrived and it is full of mDNS packets. I'am not sure for 100% but these mDNS packets probably cause your problem. I found there many mDNS connections that the system never closed.
I would prepare some simple test how to verify my suspicion. Or, If you are familiar with some firewall (Avast, windows defender etc.) you could try to set rule blocking all UDP packets from/to remote port 5353.
I did manage to figure out how to look at the firewall in Windows Defender. I found a few items of mDNS port 5353 (whatever all that means?). One of them was Microsoft Edge, which I never asked for and never wanted. I managed to find an instruction about how to really get rid of it. Did that, also disabled the other rules using mDNS Port 5353.
Now it seems that the non-paged memory leak is much better. Last night over the span of four hours it increased from 283 Mbyte to 302 Mbyte, compared to previous increases of several Gbyte in that same time span before.
For others who might still be struggling with this problem, I mention my previous solution to keep the computer from freezing up. I put a rule into the task scheduler to have the computer restart twice per day, which for me was soon enough.
-
Although the leak is much better, it is not cured. As of now after about 8 hours running the memory has increased to 450 Mbyte. Below is a listing of the highest 8 users of non-paged memory:
tag *.sys
ismc iaStorA.sys & iaStorAvc.sys
Nr22 ? findstr does not return any entries
ArL2 aswArPot.sys
ConT ?
Eo16 ?
fwLP aswNetHub.sys (this used to be a top offender)
hE20 ?
fwRN aswNetHub.sys
Hope this helps eradicate the problem completely. If I can be of further assistance, let me know.
-
this problem is why i'm uninstalling Avast. But I can't get that to work right either.
-
Dale5351, Thank you for help. We will release the fix ASAP
-
I just want to chime into say that Avast is also rendering my computer non-functional by sucking up all my CPU for the last few days. Though mine is a desktop, not a laptop. It's happened once before maybe a year ago and back then repair app worked okay. This time repair app seems to do nothing except maybe give a little breathing room before sucking up all the CPU again. (Also memory is unacceptably high- first noticeably hovering in the 800,000K when nothing much is running, but now it averages at 1,500,000 k)
I really hope this is fixed soon.
edit.
Next day. So downloaded the update. Took awhile as Avast worked against itself hogging resources, but looks like it worked. Dropped from 100% CPU and over 2 million K Memory to 0% CPU and around 70,000 K Memory.
-
Hi All, fix of extreme non-paged memory consumption related to the network was just released via automatic update. Please, check version of your Avast in the Menu->About. Build number of fixed version should be 20.8.5684.602 or higher. If it is lower, please try to manually update Avast.
-
I upgraded to 20.8.5684.602 manually (the upgrade in Avast said that I was up to date on a slightly lower version number).
After about 10 hours, my non-paged memory has grown slightly from 228 Mbyte to 292Mbyte. That is a big improvement. Tomorrow, I will stop restarting every day and see if that is stable or if it continues to grow, albeit slowly.
Looking at the process monitor I find the following tags, listed in two groups, each in order of assigned non-page memory. First I list the tags that have some driver associated with them.
tag driver
ismc iaStorA and iastoravc (this was top of the list)
etw2 aswbidsdriver, aswbidsh, and iswbidlv
fwLP aswNetHub
and then the tags for which findstr did not find a driver.
Nr22
Ar12
ConT
Eo16
He20
EtwB
Ne40
Hope this info helps.
My conclusion is that things are much better, but I'm not sure that it is solved. It may also be that things other than AVAST are contributing to the memory loss. The multiple day test will help clarify this.
-
Thank you dale5351 for your last post. Please, could you show us screenshot with the kernel pool monitor similarly as in one of your previous posts?
Paulino Sato, what about you? Did you try last version (build 20.8.5684.602)?
-
Hi,
I found the the source of the problem, is the wpad.dat file used to auto define the proxy (or no proxy).
Sorry for delay.
Version 20.8.5684.602 not solved my situation. Same behavior, soon I connect network cable Avsta start eating all memory.
It happens on some networks, not on others. Or start after some time.
My network are the culprit? Why special have on these networks?
My test procedure is this:
Disable swap/paging on window, avoid system to use paging, a avast just eat all ram and killed by the kernel (I think).
Start computer with network cable disconnected (no wifi).
Open taskmanager, and Avast GUI.
Connect network cable and watch rise of memory usage by Avast.
If have some thing on my network causing the Avast memory issue, what can be?
My firewall is a linux machine, very simple, just for NAT, no complex packet filtering, multi internet access and Squid proxy (all most disabled).
I drop all forwarding from offending host. No change.
Dropped all input to firewall. NOW, avast no eating memory.
I opened port 80, and Avast start eating memory again. What Avast accessing? Check the webserver log.
Avast getting the wpad file for proxy definition on this network. Renamed wpad.dat file, and try again.
Whitout wpad, no problem, avast try to get file, get a 404 and nothing happens.
The log on webserver (lighttpd 1.4.19):
10.0.103.91 wpad - [09/Oct/2020:09:36:43 -0300] "GET /wpad.dat HTTP/1.1" 200 94 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.3.3626.1895 Safari/537.36 Avastium (20.8.2432)"
wpad.dat content:
function FindProxyForURL(url, host)
return "DIRECT";
}
I hope this information helps to solve the problem.
Tanks, Paulino.
-
Thank you dale5351 for your last post. Please, could you show us screenshot with the kernel pool monitor similarly as in one of your previous posts?
Here you go. This is after about 15 hours running. Slight leak.
-
Here is a recent screen shot, taken today Oct 11 at 12:45 pm. Machine has been running for about 60 hours. In the past three hours, there was a big jump in Non-paged memory from 461Mbyte to 4.1Gbyte.
-
Hi,
I found the the source of the problem, is the wpad.dat file used to auto define the proxy (or no proxy).
Sorry for delay.
Version 20.8.5684.602 not solved my situation. Same behavior, soon I connect network cable Avsta start eating all memory.
It happens on some networks, not on others. Or start after some time.
My network are the culprit? Why special have on these networks?
My test procedure is this:
Disable swap/paging on window, avoid system to use paging, a avast just eat all ram and killed by the kernel (I think).
Start computer with network cable disconnected (no wifi).
Open taskmanager, and Avast GUI.
Connect network cable and watch rise of memory usage by Avast.
If have some thing on my network causing the Avast memory issue, what can be?
My firewall is a linux machine, very simple, just for NAT, no complex packet filtering, multi internet access and Squid proxy (all most disabled).
I drop all forwarding from offending host. No change.
Dropped all input to firewall. NOW, avast no eating memory.
I opened port 80, and Avast start eating memory again. What Avast accessing? Check the webserver log.
Avast getting the wpad file for proxy definition on this network. Renamed wpad.dat file, and try again.
Whitout wpad, no problem, avast try to get file, get a 404 and nothing happens.
The log on webserver (lighttpd 1.4.19):
10.0.103.91 wpad - [09/Oct/2020:09:36:43 -0300] "GET /wpad.dat HTTP/1.1" 200 94 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.3.3626.1895 Safari/537.36 Avastium (20.8.2432)"
wpad.dat content:
function FindProxyForURL(url, host)
return "DIRECT";
}
I hope this information helps to solve the problem.
Tanks, Paulino.
I confirm, it comes from the proxy !
Disabling the option "Automatically detect settings" of proxy under Windows, will no more cause the memory leak.
Activating it again, and Avast eats again all memory ...
(https://s23429.pcdn.co/wp-content/uploads/2015/11/windows-automatic-proxy-setup.png)
-
Paulino, thank you for perfect analysis and darkwaechter thank you for confirmation. Guys, please could you try to post here screenshot with the Kernel Pool Monitor?
This tool is possible to download from Internet. Unfortunately, we are still not able to reproduce issue, so this picture should tell us what exactly is leaking on your systems.
dale5351, please could you try to turn off automatic proxy detection similarly as darkwaechter? You can find it in the Start Menu->Settings->Network & Internet->Proxy.
-
I turned proxy off. Will restart, and monitor. Given that it is a slow leak now, will take a few days to be sure.
Thanks all.
-
Sorry to report -- that did not help. Computer has been on since restart for 26 hours. Memory in use has increased from 1.9 Gbyte to 2.7 Gbyte. Non-paged memory increased from 229 Mbyte to 391 Mbyte. I.e. there is still a slow leak. Some of the tags map to Avast routines, others I cannot find what *.sys they belong to.
I am wondering if the constant use of WiFi might have an impact on this problem. Is there some routine that could record cumulative usage of WiFi in the same way that PoolMonX does for memory?
-
Hi,
I take a screen shot with poolmonX, taskmgr and avast gui on screen.
I don't sure if it helps.
-
Thank You Guys, now we know that we have at least two causes of memory leaks:
1) mDNS-probably related leak in the kernel - tag fwLP. We will try to fix it ASAP.
2) Automatic proxy detection leak probably in the Avast GUI. I sent info about it to GUI team. Paulino please, could you try to make memory dump file of the leaking process? if you will turn off Avast Self-defense (Menu->Settings->Troubleshooting), it should be possible to make memory dump in the Windows Task Manager. If you right-click on the process with highest memory consumption you should see "Create memory dump" choice in pull-down menu. I will send you e-mail address by personal message. Please send us zipped memory dump file to this address.
-
Dale5351,
I sent you probably fixed Avast network driver and guide how to install it to your e-mail. Please try it and let us know if your problem is solved.
-
I have just now installed the aswNetHub you sent me. I will monitor memory usage and report back. Given that this is now a slow leak, it may take a couple of days to be sure one way or the other.
BTW -- the computer with the leak is my wife's HP running Win10 Home, 64 bit, with 8 G memory.
My computer is running Win7 Pro, 64 bit with 16G memory -- and is having no problems.
-
I'm afraid that the new aswNetHub.sys you sent has not changed the slow leak. Screen shot attached. In about 60 hours non-paged memory rose from 226Mbyte to 425Mbyte, with fwLP at the top of the list.
-
Thank you Dale5351, I sent you e-mail with instructions.
-
Hi Dale5351,
new beta 20.9.2437 (https://forum.avast.com/index.php?topic=239475.0) should work fine without extreme memory consumption. Please, you can try it if it is possible. We would very like to know if problem is really fixed.
-
I'll give it a try.
-
Hello, as Martin wrote, there are two issues. One of them is PAC file has an incorrect format or is giving syntax errors(PAC file is simple JavaScript file).
This can be verified by arbitrary online JS syntax validator f.e `https://esprima.org/demo/validate.html`
That means PAC file has to be fixed on the client side.
Petr
-
I have let that new version run for about a week.
The bad news is that there is still a slow leak. Memory usage went from 2.1G with non paged of 268M to 3.0G with non paged of 323M in seven days.
That can easily not become a problem if the computer if the computer is rebooted at least once per week.
The good news is that so far as I can tell, non of the tags in the top listing for non-paged memory belong to avast. Screen shot is attached.
-
Dale5351, thank you very much for test At least major leak looks fixed.
-
It is worth mentioning that my computers are connected to internet only by wireless. I did not have this problem before I moved and had an ethernet connection. Also, I did not have the problem on my Win7 computer.
I have been researching other virus programs, and have not yet found one I like as much as Avast -- so now I thank that I will keep Avast on both computers.
Thank you for your work.
-
Is the Problem fixed ?
We ar running Cloudacre with AV
20.8.2615
An the issue still exists.
-
Hi Dale5351,
the pool allocation tags from your screen (FMfn, MmSt, NtfF) is normal file-system cache. You can validate this by using some tool to allocate huge amount of memory (like sysinternals testlimit64.exe -v) for example. For 8GB RAM computer, allocate 7GB RAM for example (testlimit64.exe -v 7000). Then you'll see huge decrease of allocations of these tags.
-
Thanks for that info. My win10 computer seems stable, and I will be keeping Avast now. None of the other top 10 virus programs I tested worked as well for me.
-
Is the Problem fixed ?
We ar running Cloudacre with AV
20.8.2615
An the issue still exists.
Still not solved with 20.9.2437.
Maybe in the next release ::)
-
Has this issue been fixed completely yet?
-
No, still not solved in 20.10.2442 ... :-[
-
Hi,
We are also having a problem similar to this - have logged a ticket with support (we are a business cloudcare customer). The issue we are having is quite frequently throughout the day 'System' will randomly run using between 10% - 30% CPU and the machine will become pretty much unusable (very laggy). It only affects machines that are plugged into the LAN - luckily the majority of staff are working from home at the moment!
When I run Windows Performance Recorder and Analyzer we get aswNetHub.sys!<PDF not found> using a lot of resource - a quick google tells me aswNetHub.sys is Avast Network Security Driver. The majority of our devices are running build 20.8.5684.613
As soon as I uninstall Avast on a machine the problem stops, if I just connect to the wifi the problem stops - are there any fixes for this issue yet?
-
Hi,
We are also having a problem similar to this - have logged a ticket with support (we are a business cloudcare customer). The issue we are having is quite frequently throughout the day 'System' will randomly run using between 10% - 30% CPU and the machine will become pretty much unusable (very laggy). It only affects machines that are plugged into the LAN - luckily the majority of staff are working from home at the moment!
When I run Windows Performance Recorder and Analyzer we get aswNetHub.sys!<PDF not found> using a lot of resource - a quick google tells me aswNetHub.sys is Avast Network Security Driver. The majority of our devices are running build 20.8.5684.613
As soon as I uninstall Avast on a machine the problem stops, if I just connect to the wifi the problem stops - are there any fixes for this issue yet?
-> https://forum.avast.com/index.php?board=77.0
-
More than 6 months later, following problem is still not solved :-\
Hi,
I found the the source of the problem, is the wpad.dat file used to auto define the proxy (or no proxy).
Sorry for delay.
Version 20.8.5684.602 not solved my situation. Same behavior, soon I connect network cable Avsta start eating all memory.
It happens on some networks, not on others. Or start after some time.
My network are the culprit? Why special have on these networks?
My test procedure is this:
Disable swap/paging on window, avoid system to use paging, a avast just eat all ram and killed by the kernel (I think).
Start computer with network cable disconnected (no wifi).
Open taskmanager, and Avast GUI.
Connect network cable and watch rise of memory usage by Avast.
If have some thing on my network causing the Avast memory issue, what can be?
My firewall is a linux machine, very simple, just for NAT, no complex packet filtering, multi internet access and Squid proxy (all most disabled).
I drop all forwarding from offending host. No change.
Dropped all input to firewall. NOW, avast no eating memory.
I opened port 80, and Avast start eating memory again. What Avast accessing? Check the webserver log.
Avast getting the wpad file for proxy definition on this network. Renamed wpad.dat file, and try again.
Whitout wpad, no problem, avast try to get file, get a 404 and nothing happens.
The log on webserver (lighttpd 1.4.19):
10.0.103.91 wpad - [09/Oct/2020:09:36:43 -0300] "GET /wpad.dat HTTP/1.1" 200 94 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.3.3626.1895 Safari/537.36 Avastium (20.8.2432)"
wpad.dat content:
function FindProxyForURL(url, host)
return "DIRECT";
}
I hope this information helps to solve the problem.
Tanks, Paulino.
I confirm, it comes from the proxy !
Disabling the option "Automatically detect settings" of proxy under Windows, will no more cause the memory leak.
Activating it again, and Avast eats again all memory ...
(https://s23429.pcdn.co/wp-content/uploads/2015/11/windows-automatic-proxy-setup.png)
-
More than 6 months later, following problem is still not solved :-\
1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.
-
More than 6 months later, following problem is still not solved :-\
1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.
ID : 02PFY
Steps to trigger the problem in all cases :
- Disable the "Automatically detect settings" of Proxy under Windows (otherwise I cannot update Avast 20.7 to a newer version).
- Update Avast to the latest version or to any version newer than 20.7.
- Enable again the "Automatically detect settings" of Proxy.
- Open Avast GUI -> RAM usage increases quickly to 100%, pagefile will then saturated the disk and computer finally crashes.
-
More than 6 months later, following problem is still not solved :-\
1. Enable debug logging (Menu > Settings > General > Troubleshooting > Enable debug logging) and reproduce the issue.
2. Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.
ID : 02PFY
Steps to trigger the problem in all cases :
- Disable the "Automatically detect settings" of Proxy under Windows (otherwise I cannot update Avast 20.7 to a newer version).
- Update Avast to the latest version or to any version newer than 20.7.
- Enable again the "Automatically detect settings" of Proxy.
- Open Avast GUI -> RAM usage increases quickly to 100%, pagefile will then saturated the disk and computer finally crashes.
Hi, I forwarded it, let's see...
-
Hello, I'm really sorry the delay. Issue is not directly in our code (3td party lib). We are testing the new build right now. If everything goes well it should be ready for beta 21.5. I know it is still pretty far. But we need to test it properly (few weeks in internal builds).
Petr
-
Hello, I'm really sorry the delay. Issue is not directly in our code (3td party lib). We are testing the new build right now. If everything goes well it should be ready for beta 21.5. I know it is still pretty far. But we need to test it properly (few weeks in internal builds).
Petr
Thank you for the information !
I made some more tests, and I can confirm that Adobe Creative Cloud Desktop has exactly the same issue (also since some months).
Maybe they use the same third party library ::)
Will now wait your beta.
-
Hello,
On one of concerned computer, Avast has accidentally upgraded to the latest release 21.4 and I noticed that the memory problem seems to no more occur.
Can you confirm that it is solved in this version ?
-
For information, the problem did not occur since the 21.4 version ;)
Unfortunately, other software are now more and more concerned with the same issue.
Adobe Creative Cloud Desktop was the first were we identified it, and it is still not fixed !
Then it was Avast, which is now solved.
Meantime, Adobe InDesign is also concerned and not fixed.
And the latest version of Adobe Reader (october 2021) is now also concerned !
Edit : for Adobe Reader, it seams that the problem concerns the 64 bits version.
On the other hand, Google Driver Desktop has a very similar problem.
As you fixed or bypassed the problem, do you know where it comes from ?
From Avast itself ? Or from a third party library / framework ?
Better, could you directly inform Adobe, Microsoft or Google to help them for solving ?