See logcat/traces/bugreport in the attachments

Deleted: logcat.txt 357 KB

logcat.txt 357 KB View Download

Deleted: traces.txt.bugreport 2.1 MB

traces.txt.bugreport 2.1 MB Download

Deleted: traces.txt 843 KB

traces.txt 843 KB View Download

Related issues:
https://bugs.chromium.org/p/chromium/issues/detail?id=805782
https://stackoverflow.com/questions/50945853/how-to-fix-anr-issue-on-data-app-com-android-chrome-1-base-apk
https://stackoverflow.com/questions/50268578/anr-application-not-responding-crash-in-google-play-console-which-i-dont-unde
https://stackoverflow.com/questions/50905444/anr-investigating-with-trace-txt

This is somewhat similar to b/67755599 (Google internal, sorry!).

From that bug, Bo commented:

webview sends a sync IPC to the renderer process in OnBeginFrame, so that's hanging for some reason. 

Bo, is there any signal from traces.txt that looks suspicious?

chrome doesn't ship unwind tables (to reduce binary size) so debuggerd can't unwind the native stack. Top frame of the stack is generally useless since it's generally in some generic library call and doesn't indicate where the call is coming from.

Looking that traces.txt, all the relevant threads that UI thread is waiting for appears to be idle, which is weird. But either way, without a somewhat consistent repro, there isn't much we can do.

is there any public debug builds of chromium for android? we've managed to reproduce it once, but there is no new info

No, and debug builds are significantly bigger and slower such that if a problem is due to a race, then it's likely to reproduce.

I'm not sure if we publish debug symbols, but even if we do, that doesn't help in this case, since you can only symbolize that one frame which is generally unhelpful.

What needs to happen is to build a release build *with unwind tables* so that debuggerd can walk the entire native stack. Reproduce the ANR, and then symbolize the entire native stack.

So the most helpful thing you can do here is to give us exact instructions on how to reproduce this ANR. Which app, what steps, which version of webview, which version of android, what device, etc etc.

 Issue 860272  has been merged into this issue.

This is my most common ANR at this point. Anyone have any ideas? I've never had it happen to me. 

"main" prio=5 tid=1 Native
  | group="main" sCount=1 dsCount=0 obj=0x76c50608 self=0xef205400
  | sysTid=16510 nice=-4 cgrp=default sched=0/0 handle=0xf242d548
  | state=S schedstat=( 234795728987 33489457230 411477 ) utm=19868 stm=3611 core=2 HZ=100
  | stack=0xff38d000-0xff38f000 stackSize=8MB
  | held mutexes=
  #00  pc 0000000000017540  /system/lib/libc.so (syscall+28)
  #01  pc 0000000000047beb  /system/lib/libc.so (_ZL24__pthread_cond_timedwaitP23pthread_cond_internal_tP15pthread_mutex_tbPK8timespec+102)
  #02  pc 0000000000e47793  /data/app/com.android.chrome-2/base.apk (???)
  at org.chromium.ui.base.WindowAndroid.nativeOnVSync (Native method)
  at org.chromium.ui.base.WindowAndroid.a (SourceFile:142)
  at bKj.doFrame (SourceFile:37)
  at android.view.Choreographer$CallbackRecord.run (Choreographer.java:957)
  at android.view.Choreographer.doCallbacks (Choreographer.java:734)
  at android.view.Choreographer.doFrame (Choreographer.java:667)
  at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:945)
  at android.os.Handler.handleCallback (Handler.java:751)
  at android.os.Handler.dispatchMessage (Handler.java:95)
  at android.os.Looper.loop (Looper.java:154)
  at android.app.ActivityThread.main (ActivityThread.java:6776)
  at java.lang.reflect.Method.invoke! (Native method)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1518)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1408)

 Issue 881339  has been merged into this issue.

I have the same issue on my app and it seems it suddenly started on October 18th and increased day by day, and it is the top ANR on my ANR list now. I don't have much information other than the play store log below. I couldn't even create the issue myself. I can only say that I am using Admob, Facebook and Mopub to show banners and interstitials and they are using webview. 

There are other threads traces in the list but couldn't see any suspicious thread state and trace.

main" tid=1 Native 
"main" prio=5 tid=1 Native
  | group="main" sCount=1 dsCount=0 obj=0x75a367d0 self=0xac304e00
  | sysTid=30043 nice=-10 cgrp=default sched=0/0 handle=0xaf549548
  | state=S schedstat=( 4518867842 1451598315 9974 ) utm=357 stm=94 core=1 HZ=100
  | stack=0xbe797000-0xbe799000 stackSize=8MB
  | held mutexes=
  #00  pc 0000000000017778  /system/lib/libc.so (syscall+28)
  #01  pc 000000000004788d  /system/lib/libc.so (_ZL24__pthread_cond_timedwaitP23pthread_cond_internal_tP15pthread_mutex_tbPK8timespec+102)
  #02  pc 0000000000e9b2ab  /data/app/com.android.chrome-2/base.apk (???)
  at org.chromium.ui.base.WindowAndroid.nativeOnVSync (Native method)
  at org.chromium.ui.base.WindowAndroid.a (SourceFile:166)
  at bZj.a (SourceFile:16)
  at bYU.doFrame (SourceFile:22)
  at android.view.Choreographer$CallbackRecord.run (Choreographer.java:928)
  at android.view.Choreographer.doCallbacks (Choreographer.java:705)
  at android.view.Choreographer.doFrame (Choreographer.java:637)
  at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:916)
  at android.os.Handler.handleCallback (Handler.java:751)
  at android.os.Handler.dispatchMessage (Handler.java:95)
  at android.os.Looper.loop (Looper.java:154)
  at android.app.ActivityThread.main (ActivityThread.java:6816)
  at java.lang.reflect.Method.invoke! (Native method)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1565)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1453)

I have yet to reproduce it but it is my most common ANR. I even bought one of the phones that is up at the top of the report and still can't reproduce it. My app does use the WebView but now I'm wondering if it has to do with ads. 

We have the same issue. Any news on resolving this? Google is starting to punish apps for their ANR rate, we really need to understand why is this happening and how to fix this.

The issue is marked as won't fix, I recommend creating a new one if you have more information. It is my most common anr and I'm terrified of it hurting my ranking, so far it hasn't thankfully. Has it affected you already? 

Filing a new bug will just cause it to be duplicated into this. See comment 7 for more info on how to move this forward. Specifically, this bit:

So the most helpful thing you can do here is to give us exact instructions on how to reproduce this ANR. Which app, what steps, which version of webview, which version of android, what device, etc etc.

#15 I think the issue is that none of us (as far as I know) have reproduced the issue, we just get ANRs on the Play Store console. I even bought one of the phones listed there and I have yet to reproduce the issue. 

Device tested :- Samsung S8,S9,S9 plus 

=========================
ANR stack trace :- 
"main" prio=5 tid=1 Native
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x743ae538 self=0xed4ab000
  | sysTid=15670 nice=-10 cgrp=default sched=0/0 handle=0xf1a714bc
  | state=S schedstat=( 19319679915 5884419924 104161 ) utm=1204 stm=727 core=4 HZ=100
  | stack=0xff695000-0xff697000 stackSize=8MB
  | held mutexes=
  kernel: (couldn't read /proc/self/task/15670/stack)
  native: #00 pc 00019178  /system/lib/libc.so (syscall+28)
  native: #01 pc 000488f7  /system/lib/libc.so (_ZL24__pthread_cond_timedwaitP23pthread_cond_internal_tP15pthread_mutex_tbPK8timespec+102)
  native: #02 pc 00e9b133  /data/app/com.android.chrome-Hg3Iqd8xpyz0FjL9DpWwyQ==/base.apk (???)
  at org.chromium.ui.base.WindowAndroid.nativeOnVSync(Native method)
  at org.chromium.ui.base.WindowAndroid.a(SourceFile:166)
  at bZj.a(SourceFile:16)
  at bYU.doFrame(SourceFile:22)
  at android.view.Choreographer$CallbackRecord.run(Choreographer.java:909)
  at android.view.Choreographer.doCallbacks(Choreographer.java:723)
  at android.view.Choreographer.doFrame(Choreographer.java:655)
  at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:897)
  at android.os.Handler.handleCallback(Handler.java:789)
  at android.os.Handler.dispatchMessage(Handler.java:98)
  at android.os.Looper.loop(Looper.java:164)
  at android.app.ActivityThread.main(ActivityThread.java:6938)
  at java.lang.reflect.Method.invoke(Native method)
  at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)

Deleted: ADB_1-.01._15.16.44.65.txt 6.4 MB

ADB_1-.01._15.16.44.65.txt 6.4 MB View Download

Deleted: traces.txt 1.0 MB

traces.txt 1.0 MB View Download

#17 did you find a way to reproduce the issue? I have several phones I could try it on.