[Bug] AdGuard Assistant freezes after 1–2 hours, stops recognizing new app traffic

[oldip]

Please answer the following questions for yourself before submitting an issue

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

AdGuard version

4.11

Environment

• OS version: Android 14
• Device: ROG Phone 8 Pro

HTTPS filtering

• [x] yes, I do

Root access

• [ ] yes, I have it

Integration with AdGuard VPN

• [ ] yes, I do

Routing mode

Local VPN

Ad Blocking

AdGuard Base filter, AdGuard Mobile Ads filter, EasyList

Privacy

AdGuard Tracking Protection filter, AdGuard URL Tracking filter, EasyPrivacy, Legitimate URL Shortener, Peter Lowe's Blocklist

Social

AdGuard Social Media filter

Annoyances

AdGuard Annoyances filter, AdGuard Cookie Notices filter, AdGuard Popups filter, AdGuard Mobile App Banners filter, AdGuard Other Annoyances filter, Adblock Warning Removal List, Fanboy's Annoyances, EasyList Cookie List, Dandelion Sprout's Annoyances List

Security

No response

Language-specific

AdGuard Chinese filter, EasyList China

Other

Filter unblocking search ads and self-promotion

Which DNS server do you use?

DNS protection disabled

DNS protocol

None

Custom DNS

NEO DEV HOST Cats Team AdRules AdBlock List Plus

What Stealth Mode options do you have enabled?

No response

Issue Details

Steps to reproduce:

1. Restart the phone.
2. Open AdGuard Assistant, it can correctly recognize recently used apps.
3. After 1–2 hours, the Assistant freezes: it no longer recognizes new application traffic or websites.
4. However, in Recent Activity (last 10,000 requests), network activity and blocked requests are still recorded.

Expected Behavior

AdGuard Assistant should continue to update and display new application traffic and website filtering information without freezing, even after the device has been running for a long time.

Actual Behavior

After 1–2 hours, AdGuard Assistant stops recognizing new application traffic and websites, even though AdGuard itself is still processing requests (as confirmed in the “Recent Activity” log).

Screenshots

Screenshot 1 – Assistant showing no new recognized apps

Screenshot 2 – Recent Activity still logging requests

Additional Information

No response

[ESurina]

In order to troubleshoot this issue, we need to get your application logs.

Here's what we need you to do:

1. Enable debug logging: Settings -> General -> Advanced -> Logging level -> Debug.
2. Reproduce the problem, then remember the exact time when it happened.
3. Collect logs: Settings -> General -> Advanced -> Export logs and system info.
4. Send this file to [email protected]:
   • include [android] keyword and 5846 in the subject of your email
   • specify the exact time when the issue occurred

[oldip]

I tried enabling debug logging as requested, but unfortunately it doesn’t work. When I switch the logging level to Debug, the AdGuard app immediately crashes on startup (auto force close).

The only way to open AdGuard again is to disable logging (reset it back to the default level). Because of this, I cannot reproduce the issue with debug logging enabled.

I also recorded a video showing the crash when enabling debug logging.

https://github.com/user-attachments/assets/1bc1bf30-c300-48dc-a23a-031595334a31

[Lwb828]

This problem will also occur in the 4.12 stable release.

[ESurina]

To understand why your app is crashing, we need to get your system logs.

Here is how to collect them: https://adguard.com/kb/adguard-for-android/solving-problems/logcat/

Send logs to [email protected]: - include [android] keyword and 5846 in the subject of your email - specify the exact time when the issue occurred

[ESurina]

We don't see any crashes in your system logs, so we have one more request. Could you please enable debug logging level in AdGuard and disable it after crash. Then:

1. Collect logs: Settings -> General -> Advanced -> Export logs and system info.
2. Send this file to [email protected]:
   • include [android] keyword and 5846 in the subject of your email
   • specify the exact time when the issue occurred

[oldip]

Thanks a lot to the AdGuard team for your help! After the last update, the issue has been fully resolved — everything works fine now.

I noticed that some other users still seem to experience a similar problem, so I wasn’t sure whether I should close this issue myself. That’s why I didn’t reply earlier.

Thanks again for your support and quick fixes!

[Lwb828]

In my recent usage of the stable version of the AdGuard app for Android, I've encountered this bug multiple times. The bug doesn't seem to be related to the phone's screen-off time or whether I open/enter the AdGuard app. Instead, it appears to be connected to the update frequency of AdGuard's rules. If I update the rules within a day, the bug doesn't occur that day. However, if I don't update the rules, the bug might appear after a day. I'm not certain if this speculation is correct, but fortunately, this issue seems to be absent in the nightly builds.I use AI to translate Chinese into English.

[Lwb828]

Oh, this bug also appears in the latest nightly build of AdGuard. However, I might have been wrong earlier—it doesn't seem to be related to rule updates. But this bug is extremely difficult to trigger in this nightly build. I'm using an AI-generated translation; please bear with me if there are any issues.

[Lwb828]

"Sorry, but since I cleared the data on the AdGuard app on both of my devices, capturing this bug might take a very long time. Currently, my spare device is trying to capture the bug using the system's built-in log recording app and AdGuard's debug logs, but it's quite difficult to trigger and record."

[ESurina]

Once you are able to reproduce the bug, please do the following:

1. Collect logs: Settings -> General -> Advanced -> Export logs and system info.

2. Send this file to [email protected]:

• include [android] keyword and 5846 in the subject of your email
• specify the exact time when the issue occurred

[Lwb828]

[Lwb828]

I have two phones, a Meizu Lucky08 and a Meizu 20, both running the latest internal testing system.

[Lwb828]

[Lwb828]

When capturing the bug log of AdGuard Nightly, it was found that AdGuard may crash due to excessive memory usage caused by built-in debug logging, leading the app to close and stop running. Logs have been exported. It's unclear if this bug affects other functions, but one thing is certain: AdGuard can consume up to 2GB of memory while recording logs, indicating active operation, making it difficult to capture this issue.Furthermore, I am unable to submit feedback through the AdGuard nightly version and am uncertain whether this is a bug.

[Lwb828]

One fortunate thing is that I captured a relevant bug in the AdGuard nightly version. The bug occurred around 4:07 PM on November 24, 2025, in version AdGuard 4.14.nightly9. Additionally, when AdGuard is in debug log recording mode, it may consume up to 2GB of memory in the background and could crash or stop functioning. The app will automatically restart protection after reopening. This issue appears unrelated to AdGuard bug number 5846, but might still be connected. I'm unsure whether to report the corresponding log, which has already been exported.

[ESurina]

Could you please tell me, did you mean that the assistant sometimes stops working for you too? Which apps do you use to detect that the assistant stops monitoring your traffic?

[Lwb828]

Could you please tell me, did you mean that the assistant sometimes stops working for you too? Which apps do you use to detect that the assistant stops monitoring your traffic?

In fact, I didn’t know it would crash and stop running. I found out because I enabled "Developer Options" and checked "Running Services," where I saw AdGuard in debug mode using up to 2GB of RAM. I ignored it, but I had "Always-on VPN" and "Block connections without VPN" enabled. So when AdGuard wasn't running (no process), I got alerts. I’ve seen this high memory usage (2GB or 1.9GB) twice, and eventually the process disappeared. I've also seen normal usage around 600MB, which seems fine. I'm unsure if it's an AdGuard issue or Android limitation, but I wanted to report it. Also, I can notice when AdGuard stops filtering over time (despite the process still running) mainly due to those two features—they make network issues obvious 😂😂

[ESurina]

This issue is dedicated to a problem with the assistant, so please create a separate one. High memory consumption is normal for debug-level logging. However, the application shouldn't crash or stop filtering, so please mention this specific problem in the title of the new issue.

[Lwb828]

This issue is dedicated to a problem with the assistant, so please create a separate one. High memory consumption is normal for debug-level logging. However, the application shouldn't crash or stop filtering, so please mention this specific problem in the title of the new issue.

In fact, the issue of AdGuard stopping filtering after prolonged use has occurred in the nightly version; has this been resolved?