RAM usage problem after upgra NEW Avast Version 20.7.2425

[dale5351]

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?

[Paulino Sato]

Hi,
I take a screen shot with poolmonX, taskmgr and avast gui on screen.
I don't sure if it helps.

[MartinK]

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.

[MartinK]

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.

[dale5351]

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.

[dale5351]

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.

[MartinK]

Thank you Dale5351, I sent you e-mail with instructions.

[MartinK]

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.

[dale5351]

I'll give it a try.

[petr blatny]

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

[dale5351]

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.

[MartinK]

Dale5351, thank you very much for test At least major leak looks fixed.

[dale5351]

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.

[loading]

Is the Problem fixed ?

We ar running Cloudacre with AV
20.8.2615

An the issue still exists.

[Spec8472]

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.