Maxim Topciu

you can download it here https://github.com/AdguardTeam/AdguardBrowserExtension/releases/tag/v4.1.22 Maybe the next week you can help us to detect this bug? can you write me an email at [email protected]?

I need your help to debug this issue on your computer via anydesk if it is possible.

> @Versty > > Hello, it's been more than 30 days since this issue, have you investigated the cause? Hi, @accountforadg! Currently, this issue is not on our top priority...

@accountforadg try to start from our knowledge base https://kb.adguard.com/en/general/how-to-create-your-own-ad-filters

There are compatibility notes in the end of description of the each modifier in the AdGuard rules. They state that these modifiers are not fully supported in the extension yet....

@DerFreischutzTKH, @pejotigrek AdGuard's allowlist doesn't support rules, only plain text with domain names (`example.org`). Recently, we've added support for wildcards (`*.example.com`), which might explain why your rules started turning protection...

> is it possible that rules worked before? It's unlikely that these rules worked as intended before. If they did, it must have been quite some time ago.

After peak passes does the memory consumption returns to the previous values? Could you please collect profile during memory peaks?

Hi, @Steven-DD Are these logs visible if you close the filtering log window?

It seems that there is a bug. Just wanted to clarify, is this option enabled at you? If yes, then disable it, and reload extension (or browser), it should help....