High number of hard pagefaults of AG service process when measuring with LatencyMon app

[trparky]

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

8.0.5284.0

Browser version

Microsoft Edge 143.0.3650.80

OS version

Windows 11, 25H2 (26200.7462)

Traffic filtering

• yes, I do

Ad Blocking

No response

Privacy

No response

Social

No response

Annoyances

No response

Security

No response

Other

No response

Language-specific

No response

Which DNS server do you use?

AdGuard DNS

DNS protocol

DNS-over-TLS

Custom DNS

No response

What Stealth Mode options do you have enabled?

No response

Support ticket ID

No response

Issue Details

Steps to reproduce:

1. Load up LatencyMon.
2. Let it analyze your system.
3. Watch how many hard page faults that the AdGuard Service is producing.

Expected Behavior

No response

Actual Behavior

...

Screenshots

Additional Information

My system uptime is as follows...
PS C:\Users\user> uptime

Days : 0
Hours : 3
Minutes : 27
Seconds : 54
Milliseconds : 0
Ticks : 124740000000
TotalDays : 0.144375
TotalHours : 3.465
TotalMinutes : 207.9
TotalSeconds : 12474
TotalMilliseconds : 12474000

With the system being up and online for only three hours, 11.9 million hard page faults is not too good. This can cause a lot of issues including audio dropouts, glitches, and various other things that might need to be time-critical and uninterrupted.

[trparky]

Several hours later, it's up to nearly 44 million page faults.

According to System Informer, a kind of software that's like Task Manager but on steroids, I can look into programs that use .NET as the backing. According to it...

Total Bytes Allocated (since start), 688.52 GB
Total Bytes Allocated for Large Objects (since start), 601.26 GB

Something isn't right here.

[Terepin]

Could be related to my issue: it is constantly writing to C drive for some unknown reason.

[RedPandaSupreme]

I noticed this as well. Something is really wrong here!

[KolbasovAnton]

@trparky Greetings. The latest nightly version shows the same results for You? I tried to measure it with LatencyMon and got only ~5k pagefaults after an hour of recording.

[trparky]

Five thousand page faults in an hour isn't good. It means that data is being paged out to the page file far more often than it should be and indicates a memory leak somewhere in the code of the AdGuardSVC.

[KolbasovAnton]

Thank you all for the reports. Honestly, it doesn't look like bug and can be explained as Windows specifically offloads part of the AdGuard application's memory to disk so that it consumes less RAM. When this memory is needed again, it is loaded back, which LatencyMon sees as a hard page fault. This is normal and does not mean a memory leak.
But surely, we will investigate this issue.