As per logs following analysis is found .

#Main UI thread is waiting for CountDownLatch to complete it's execution in ChromeBrowser application (org.chromium.chrome.browser.ChromeTabbedActivity).

Both UI thread and CountDownLatch are waiting on same mutex to achieve lock.


"main" prio=5 tid=1 Waiting
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x737277b0 self=0xe5f8f000
  | sysTid=1488 nice=-10 cgrp=default sched=0/0 handle=0xe99854a4
  | state=S schedstat=( 2115777344 491393294 1163 ) utm=190 stm=21 core=2 HZ=100
  | stack=0xff231000-0xff233000 stackSize=8MB
  | held mutexes=
  at java.lang.Object.wait(Native method)
  - waiting on <0x0d7c2458> (a java.lang.Object)
  at java.lang.Thread.parkFor$(Thread.java:2137)
  - locked <0x0d7c2458> (a java.lang.Object)
  at sun.misc.Unsafe.park(Unsafe.java:358)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:190)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:868)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1021)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1328)
  at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:232)
  at bAB.c(SourceFile:52)
  at bAB.d(SourceFile:62)
  at bAB.b(SourceFile:40)
  at org.chromium.chrome.browser.ChromeTabbedActivity.P(SourceFile:168)
  at aMX.run(SourceFile:3)
  at aMI.run(SourceFile:7)
  at android.os.Handler.handleCallback(Handler.java:790)
  at android.os.Handler.dispatchMessage(Handler.java:99)
  at android.os.Looper.loop(Looper.java:164)
  at android.app.ActivityThread.main(ActivityThread.java:6528)
  at java.lang.reflect.Method.invoke(Native method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

This issue looks similar to  issue 890194 , hence cc'ing  bsazonov# for further inputs on this issue.

Thanks!

Can you reproduce the issue on M-71?

Also, I can't deobfuscate the stacktrace from #1. Can you please double-check Chrome version, OS version and CPU architecture? Have you installed Chrome from Play Store?

Issue is reported in Chrome version: 70.0.3538.110
After updating chrome from play store version is 71.0.3578.99

Please find comments below.
//Can you reproduce the issue on M-71? - 
Please let me know M-71 drop is in which version of Chrome.

//Also, I can't deobfuscate the stacktrace from #1. Can you please double-check Chrome version, OS version and CPU architecture?
Chrome version: 70.0.3538.110  
OS Version: 8.1.0
CPU architecture - armv8-a

//Have you installed Chrome from Play Store?
Yes.

Please find attached file for more information.

Deleted: chrome-version.png 67.4 KB

	chrome-version.png 67.4 KB View Download

I still can't deobfuscate the stacktrace. Anyway, I've seen similar stacktraces in my local runs, so I'm assuming this is from SigninPromoUtil or NTP signin promo. There's already a bug to track ANRs from AccountManagerFacade, so I'm marking this as a duplicate.

H,
Can you please let me know what it means by M-71? what version it relates to?

thanks,
Himanshu

Sorry for being unclear.

In Chrome terminology, M-71 is Milestone 71, so it's Chrome with major version of 71 (for example, 71.0.3578.99 that you've mentioned).