Nikita Gorskikh
Nikita Gorskikh
@khafan11 Short explanation: you'll have to add `local.adguard.org` to the "no proxy" list. The proxy can't connect to it since it is a special "black hole" address. Longer explanation: Normally,...
Hi! Is my understanding correct that as soon as you enable AdGuard, `com.adguard.mac.adguard.network-extension`'s memory consumption starts rising, seemingly without any other actions on your part, and does not stop until...
@Oleg-Chashko @aliafshany Greetings! Sorry for the wait. We've managed to find and fix a few insignificant memory "leaks", but we haven't been able to reproduce the issues mentioned in this...
@aliafshany Updated the previous comment.
@aliafshany Try recording for a few minutes instead of a few hours? :)
@aliafshany @Oleg-Chashko There's a new nightly version out: `2.9.0.1186`, please try updating to it and see if it leaks more/less/the same. @aliafshany If the aformentioned version is still leaking, we'd...
@ameshkov Shouldn't we flush the cache on network change anyway?
`testUpstream` accepts full upstream settings, including timeout :) The idea is that the same settings should be passed to `testUpstream` that would be used to initialize the proxy. And we...
Oh, I see the problem: there's an IPv6 "connectivity check" (to decide if bootstrapper should make AAAA queries) that's actually trying to do a DNS exchange over UDP over IPv6...