New beta version 21.2.2455

[KarelŠťavík]

Hi everyone,

there is a new beta version ready - 21.2.2455 (build 21.2.6096).

What was fixed

• final tuning before release to public (some minor setup changes)

Download links
Avast free https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_ONLINE/build_BETA
Avast premium https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_APR/platform_WIN/installertype_ONLINE/build_BETA

Enjoy this beta!
We are looking forward to your feedback.

AVAST Team

[schmidthouse]

Working fine on both machines

[NON]

Thanks for the new beta

[NON]

After reboot, AvastUI automatically opened, and it says there are 7 Wi-fi inspector alerts. All of them shows the same time.
Just to be sure, I don’t perform any Wi-fi inspector scan recently. Strange. :-\

[Asyn]

Thanks Karel, the beta is running smooth here.

[schmidthouse]

Just a question, if upgrading from Premium beta to Ultimate would one be Uninstalling the beta application??

[strakl]

Thanks for the beta. Working fine here.

[darkwaechter]

Still have following memory leak since 20.7 …

@darkwaechter post:73

@Paulino Sato post:70

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

[Asyn]

@schmidthouse post:6

Just a question, if upgrading from Premium beta to Ultimate would one be Uninstalling the beta application??

In short, no. The AV component is the same in both products.

[schmidthouse]

@Asyn post:9

@schmidthouse post:6

Just a question, if upgrading from Premium beta to Ultimate would one be Uninstalling the beta application??

In short, no. The AV component is the same in both products.

Thanks for the clarification, I figured as much but wasn’t totally positive.

[Asyn]

@schmidthouse post:10

@Asyn post:9

@schmidthouse post:6

Just a question, if upgrading from Premium beta to Ultimate would one be Uninstalling the beta application??

In short, no. The AV component is the same in both products.

Thanks for the clarification, I figured as much but wasn’t totally positive.

You’re welcome.