ANR (Application not responding) error in AdGuard for Samsung Internet Android
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.9.50
Environment
- OS version: Android 15 (SDK 35)
- Device: Samsung Galaxy M36 (SM-M366B)
- OneUI version: 7.0
HTTPS filtering
- [ ] yes, I do
Root access
- [ ] yes, I have it
Integration with AdGuard VPN
- [ ] yes, I do
Routing mode
Local VPN
Ad Blocking
No response
Privacy
No response
Social
No response
Annoyances
No response
Security
No response
Language-specific
No response
Other
No response
Which DNS server do you use?
DNS protection disabled
DNS protocol
None
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Issue Details
Steps to reproduce:
- Download the AdGuard for Samsung Internet apk
- Run the ACT stress test (developed by Samsung's internal QA team)
- ANR occurred
Expected Behavior
The crash due to ANR should not occur.
Actual Behavior
ANR crash callstack:
----- pid 23916 at 2025-06-01 16:10:10.969576189+0530 -----
Cmd line: com.adguard.android
Build fingerprint: 'samsung/m36xins/m36x:15/AP3A.240905.015.A2/M366BXXU1AYE5_ODM1AYE5:user/release-keys'
ABI: 'arm64'
Build type: optimized
Debug Store: 1,0,253021287::
suspend all histogram: Sum: 3.171ms 99% C.I. 2us-1799.199us Avg: 211.400us Max: 1857us
DALVIK THREADS (27):
"main" prio=5 tid=1 Native
| group="main" sCount=1 ucsCount=0 flags=1 obj=0x729a8f98 self=0xb40000789f67cbe0
| sysTid=23916 nice=-10 cgrp=top-app sched=0/0 handle=0x7a51b34d28
| state=S schedstat=( 544090355 24103514 1786 ) utm=27 stm=26 core=6 HZ=100
| stack=0x7fdcd6e000-0x7fdcd70000 stackSize=8188KB
| held mutexes=
native: #00 pc 0008169c /apex/com.android.runtime/lib64/bionic/libc.so (syscall+28) (BuildId: 21a82e670fd9b8294d92357326d57ab2)
native: #01 pc 0022a29c /apex/com.android.art/lib64/libart.so (art::ConditionVariable::WaitHoldingLocks+136) (BuildId: 4ccb65ae9ac5ad5da3af5a342d5b0b92)
native: #02 pc 007519f0 /apex/com.android.art/lib64/libart.so (art::JNI
"threadmanager-multiple-pool-4-thread-2" prio=5 tid=19 Blocked | group="main" sCount=1 ucsCount=0 flags=1 obj=0x141a8e10 self=0xb40000789f6c5c00 | sysTid=23946 nice=0 cgrp=top-app sched=0/0 handle=0x76c2aac5f0 | state=S schedstat=( 6148693 1750040 16 ) utm=0 stm=0 core=7 HZ=100 | stack=0x76c26a9000-0x76c26ab000 stackSize=4109KB | held mutexes= at com.adguard.mobile.multikit.common.boot.AbstractLoader.g(AbstractLoader.kt:18)
- waiting to lock <0x07645340> (a java.lang.Object) held by thread 15 at com.adguard.mobile.multikit.common.boot.AbstractLoader.f(AbstractLoader.kt:168) at com.adguard.mobile.multikit.common.boot.AbstractLoader.d(AbstractLoader.kt:20) at com.adguard.mobile.multikit.common.boot.AbstractLoader.c(AbstractLoader.kt:30) at com.adguard.mobile.multikit.common.boot.AbstractLoader.d(AbstractLoader.kt:24) at com.adguard.mobile.multikit.common.boot.AbstractLoader.e(AbstractLoader.kt:8) at com.adguard.android.ui.activity.SplashActivity.p(SplashActivity.kt:13) at com.adguard.android.ui.activity.SplashActivity.r(SplashActivity.kt:98) at com.adguard.android.ui.activity.SplashActivity.n(SplashActivity.kt:1) at com.adguard.android.ui.activity.SplashActivity$c.invoke(SplashActivity.kt:6) at com.adguard.android.ui.activity.SplashActivity$c.invoke(SplashActivity.kt:1) at E2.m$g.invoke(ExecutorService.android.kt:3) at E2.m.i(ExecutorService.android.kt:15) at E2.m.b(ExecutorService.android.kt:1) at E2.h.run(R8$$SyntheticClass:5) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487) at java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644) at java.lang.Thread.run(Thread.java:1012) DumpLatencyMs: 320.996
Screenshots
Screenshot 1
Additional Information
No response
Could you please check if this problem exists on the latest Nightly version?
@h4jani I remind you to check the latest Nightly version.
Please reopen the issue if the problem reoccurs on the latest Nightly version.