Input dispatching timed out ANR

Solar2D Android
#1

Hy there, we are trying to clean all crashes and ANR and we found some ANR, all have the same error title in play developer console, but the details are different on each one.

The error message is:

Input dispatching timed out (Waiting to send key event because the focused window has not finished processing all of the input events that were previously delivered to it. Outbound queue length: 0. Wait queue length: 2.)

The wait length is diferent across the errors.

Here are the details of some of the errors:

https://pastebin.com/gpHmfwv4

https://pastebin.com/7h2umqQU

https://pastebin.com/HEQeykmf

Is this problem in my code or a normal behavior?

Thanks

Input dispatching timed out (Waiting to send key event because the focused window has not finished processing all of the input events that were previously delivered to it. Outbound queue length: 0. Wait queue length: 2.)

#2

What version of Corona are you using to build these apps?

Thanks

Rob

#3

Hello Rob, we are using 2018.3350

Regards

#4

We have produced nearly 100 daily builds since 3350. I don’t know how many Google ANR/Crash fixes we’ve made since 3350, but it would be useful to update to a later daily build and see if we’ve already addressed this.

It would also be helpful to see your build.settings to see what plugins you’re using.

Rob

#5

Ok, rob, we will try to release an update using the latest daily build available and lets see whats happen.

This is our build.settins file:

https://pastebin.com/Xu7tV0rH

Regards

#6

Let us know the results. I don’t see anything alerting in your plugins.

Rob

#7

Input dispatching timed out is ALWAYS because of ads. if a new daily build will help is doubtful (unless you remove admob).

do share your results though

#8

Hey guys, bad news. We released a new version using 2018.3452 but the problem still there.

We have a lot of ANR reports, here are some of the latest reports.

https://pastebin.com/hpCKeN3p

https://pastebin.com/q9AGSZue

https://pastebin.com/T0tsL2rd

https://pastebin.com/qKKDpSgb

Is there anything that i can do to resolve this ANR?

Thanks.

#9

What plugins are you using?

Can you post your current build.settings?

Thanks

Rob

#10

Hy Rob, is the same that i posted before. Here is the build settings:

https://pastebin.com/Xu7tV0rH

#11

Hello to everyone, any idea in this issue. We still having the same ANRs. SGS said that this ANRs are caused by ads, this is the way that we use them:

-We are using only interstitial ads by admob.

-We are handling scene:create event, in “did” phase we call admob.show( “interstitial” ).

-When the intersticial is closed then we load a new one to use in the next screen.

-Sometimes when the user finish the level and play it again we do not change the scene, just reload it with new parameters. In that case we are calling to admob.show( “interstitial” ).

Is this correct or may be you know a better way? It looks pretty simple to me and i not seeing how can this code generate an ANR.

Thanks!

#12

I updated Vungle to their latest build and while crashes are greatly reduced, ANRS have more than doubled.

Quite why an ad can’t play without issues is beyond me!

#13

Hello guys, Any update on this issue. I have lot of reports about this issue. I don’t use ads in my project.

These are the plugins I use.

 ["plugin.notifications.v2"] = { publisherId = "com.coronalabs" }, ["plugin.google.iap.v3"] = { publisherId = "com.coronalabs", supportedPlatforms={ android=true } }, ["CoronaProvider.native.popup.social"] = { publisherId = "com.coronalabs" }, ["plugin.zip"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true, osx=true, win32=true } }, ["CoronaProvider.native.popup.activity"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, }, }, ["plugin.reviewPopUp"] = { publisherId = "tech.scotth", },

Here are complete details from play.store.

 

Input dispatching timed out (Waiting to send key event because the focused window has not finished processing all of the input events that were previously delivered to it. Outbound queue length: 0. Wait queue length: 5.), VisibleToUser
com.ansca.corona.CoronaActivity

"main" prio=5 tid=1 Native | group="main" sCount=1 dsCount=0 flags=1 obj=0x7409cf70 self=0xa743b000 | sysTid=30837 nice=0 cgrp=default sched=0/0 handle=0xaba60494 | state=S schedstat=( 18278592805 4315530018 43494 ) utm=1208 stm=618 core=5 HZ=100 | stack=0xbe480000-0xbe482000 stackSize=8MB | held mutexes= #00 pc 0000000000019d14 /system/lib/libc.so (syscall+28) #01 pc 000000000001d047 /system/lib/libc.so (\_\_futex\_wait\_ex(void volatile\*, bool, int, bool, timespec const\*)+86) #02 pc 00000000000629e7 /system/lib/libc.so (pthread\_cond\_wait+32) #03 pc 00000000024c14e3 /data/app/com.android.chrome-ztOIE6cfpW6EwPhLa5lbsw==/base.apk (offset 1ee5000) (???) at org.chromium.android\_webview.AwContents.nativeOnDraw (Native method) at org.chromium.android\_webview.AwContents.a (PG:1011) at aHo.a (PG:74) at com.android.webview.chromium.WebViewChromium.onDraw (PG:1019) at android.webkit.WebView.onDraw (WebView.java:2984) at android.view.View.draw (View.java:20215) at android.view.View.updateDisplayListIfDirty (View.java:19090) at android.view.View.draw (View.java:19943) at android.view.ViewGroup.drawChild (ViewGroup.java:4336) at android.view.ViewGroup.dispatchDraw (ViewGroup.java:4115) at android.view.View.updateDisplayListIfDirty (View.java:19081) at android.view.View.draw (View.java:19943) at android.view.ViewGroup.drawChild (ViewGroup.java:4336) at android.view.ViewGroup.dispatchDraw (ViewGroup.java:4115) at android.view.View.updateDisplayListIfDirty (View.java:19081) at android.view.View.draw (View.java:19943) at android.view.ViewGroup.drawChild (ViewGroup.java:4336) at android.view.ViewGroup.dispatchDraw (ViewGroup.java:4115) at android.view.View.updateDisplayListIfDirty (View.java:19081) at android.view.View.draw (View.java:19943) at android.view.ViewGroup.drawChild (ViewGroup.java:4336) at android.view.ViewGroup.dispatchDraw (ViewGroup.java:4115) at android.view.View.updateDisplayListIfDirty (View.java:19081) at android.view.View.draw (View.java:19943) at android.view.ViewGroup.drawChild (ViewGroup.java:4336) at android.view.ViewGroup.dispatchDraw (ViewGroup.java:4115) at android.view.View.updateDisplayListIfDirty (View.java:19081) at android.view.View.draw (View.java:19943) at android.view.ViewGroup.drawChild (ViewGroup.java:4336) at android.view.ViewGroup.dispatchDraw (ViewGroup.java:4115) at android.view.View.draw (View.java:20218) at com.android.internal.policy.DecorView.draw (DecorView.java:819) at android.view.View.updateDisplayListIfDirty (View.java:19090) at android.view.ThreadedRenderer.updateViewTreeDisplayList (ThreadedRenderer.java:686) at android.view.ThreadedRenderer.updateRootDisplayList (ThreadedRenderer.java:692) at android.view.ThreadedRenderer.draw (ThreadedRenderer.java:801) at android.view.ViewRootImpl.draw (ViewRootImpl.java:3350) at android.view.ViewRootImpl.performDraw (ViewRootImpl.java:3154) at android.view.ViewRootImpl.performTraversals (ViewRootImpl.java:2523) at android.view.ViewRootImpl.doTraversal (ViewRootImpl.java:1494) at android.view.ViewRootImpl$TraversalRunnable.run (ViewRootImpl.java:7288) at android.view.Choreographer$CallbackRecord.run (Choreographer.java:949) at android.view.Choreographer.doCallbacks (Choreographer.java:761) at android.view.Choreographer.doFrame (Choreographer.java:696) at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:935) at android.os.Handler.handleCallback (Handler.java:873) at android.os.Handler.dispatchMessage (Handler.java:99) 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)
#14

Hello usmanmughal.uog, forget Corona and try to move to Unity. We are still having a lot of anrs and crashes in our app under corona, after months of questions in this forum they cannot address the issues.

Good luck!

#15

Corona is getting more stressful everyday, there are a lot of issues. No matters how many times you post here, no one helps. No reply no addressing to the problems.

 Thank you Corona for making it this much better. I have started some 4-5 threads on forum but no one got solved yet.

#16

We are solely focused on meeting the Google 64-bit requirement. That’s the most important thing for the community right now. I’m hoping that we can get Pie support in shortly there after which I hope will address all these Android 9 issues.

Rob

#17

I understand @Rob, this is good to hear that all the android 9 issues will get resolved with 64 Bit support.

I will not ask for the ETA or anything like that. I will just ask one thing, Do you believe that 64 Bit support will be done well in time?

Because if you believe this then we believe you.

#18

There is a big difference between “I hope they will be addressed” and they “will get resolved”. But targeting SDK 28 (Pie) and the fact that most of the ANR’s/Crashes seem to happen on Android 9 and using newer 64-bit libraries sounds like a recipe for success. So I don’t know that they will be solved, but we are changing a lot of the parts that help modernize the APK’s so we will cross our fingers and “hope”. If it doesn’t then we will have to address them.

#19

What version of Corona are you using to build these apps?

Thanks

Rob

#20

Hello Rob, we are using 2018.3350

Regards