Please answer the following questions for yourself before submitting an issue

• Filters were updated before reproducing an issue
• I checked the knowledge base and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard version

v4.6.4 (204) or newer

Issue Details

The issue was originally reported by @derKief, check out the logs analysis here:
#5499 (comment)

To sum it up, AdGuard v4.6 consumes several times more than v4.5

UPDATE:
If you look through the issue comments, you'll see that we found two different issues here.

1. One issue is due to a race condition in the TCP/IP stack implement. VERY random bug, hard to catch.
2. The other issue is due to the statistics implementation. Temporary solution: clear stats.

Actual Behavior

The usage should be more or less the same in v4.5 and v4.6.