ANR - Input dispatching timed out

757 views
Skip to first unread message

Anton Petrov

unread,
Mar 22, 2023, 10:05:58 AM3/22/23
to Google Mobile Ads SDK Developers
The main thread is blocked, waiting on a native synchronisation routine such as a mutex.

Native synchronisation routines don't provide details on the exact lock or where it is being held. Find the locked mutex in your source, and then locate other code locations where it is being acquired. You can use Android Studio's profiler to detect potential lock contentions if multiple threads frequently compete for the same lock.

"main" tid=1 Native
  #00  pc 0x000000000001f06c  /system/lib64/libc.so (syscall+28)
  #01  pc 0x00000000000221bc  /system/lib64/libc.so (__futex_wait_ex(void volatile*, bool, int, bool, timespec const*)+140)
  #02  pc 0x0000000000080f74  /system/lib64/libc.so (pthread_cond_wait+60)
  #03  pc 0x000000000226c638  /data/app/com.android.chrome-d9RFNtM7wM3QchgFJt6FUA==/base.apk
  at J.N.M9iLjy6T (Native method)
  at org.chromium.content.browser.BrowserStartupControllerImpl.i (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:82)
  at yp.run (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:59)
  at org.chromium.base.ThreadUtils.f (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:7)
  at org.chromium.android_webview.AwBrowserProcess.k (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:23)
  at com.android.webview.chromium.M.e (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:146)
  at com.android.webview.chromium.M.b (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:172)
  at com.android.webview.chromium.WebViewChromiumFactoryProvider.k (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:11)
  at com.android.webview.chromium.WebViewChromium.init (chromium-Monochrome.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:89)
  at android.webkit.WebView.<init> (WebView.java:678)
  at android.webkit.WebView.<init> (WebView.java:604)
  at android.webkit.WebView.<init> (WebView.java:587)
  at android.webkit.WebView.<init> (WebView.java:574)
  at android.webkit.WebView.<init> (WebView.java:564)
  at com.google.android.gms.ads.internal.webview.ac.<init> (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922:1)
  at com.google.android.gms.ads.internal.webview.r.a (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922:4)
  at com.google.android.gms.ads.internal.webview.v.a (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922:4)
  at com.google.android.gms.ads.internal.js.l.<init> (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922:3)
  at com.google.android.gms.ads.internal.js.p.run (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922:2)
  at android.os.Handler.handleCallback (Handler.java:873)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at atp.a (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922)
  at com.google.android.gms.ads.internal.util.f.a (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922:1)
  at atp.dispatchMessage (:com.google.android.gms.policy_ads_fdr_dynamite@230500000@230500000057.504263922.504263922)
  at android.os.Looper.loop (Looper.java:193)
  at android.app.ActivityThread.main (ActivityThread.java:6923)
  at java.lang.reflect.Method.invoke (Native method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:870)

Mobile Ads SDK Forum Advisor

unread,
Mar 22, 2023, 3:46:54 PM3/22/23
to anton....@colossi.games, google-adm...@googlegroups.com

Hello Anton,

Welcome to Mobile Ads SDK support team. Thank you for reaching out to us.

Would you be able to provide more context on your posted issue here? Is this an issue with Mobile Ads SDK? Moreover, is this a crash issue? Kindly provide the below details as well so we can further investigate.

  • sample project implementation where the issue is reproducible
  • app id
  • ad unit id
  • affected device details (name and version)
  • full stack trace


On the other hand, if this is a response to an existing thread, would you be able to share to us the link if it is from forum or the subject title itself so we can associate it to the correct thread?

You may send the requested details privately via "Reply to Author" button or with the below process.

If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

 

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002k1pgFQAQ&entry.80707362=00172009

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Regards,

Google Logo Mobile Ads SDK Team


ref:_00D1U1174p._5004Q2k1pgF:ref
Reply all
Reply to author
Forward
0 new messages