How to decipher Google Errors?

Solar2D Android
#1

I’d like to ask if these types of errors are my fault or are a problem between google and corona?  How does one go about debugging these?  (I seem to get these two consistently)

Thanks, Greg

java.lang.IllegalArgumentException :

 

at com.google.android.gles_jni.EGLImpl.eglGetConfigAttrib (Native Method)

 

at com.ansca.corona.graphics.opengl.GLSurfaceView$ComponentSizeChooser.findConfigAttrib (GLSurfaceView.java:996)

 

at com.ansca.corona.graphics.opengl.GLSurfaceView$ComponentSizeChooser.chooseConfig (GLSurfaceView.java:957)

 

at com.ansca.corona.graphics.opengl.GLSurfaceView$BaseConfigChooser.chooseConfig (GLSurfaceView.java:887)

 

at com.ansca.corona.graphics.opengl.GLSurfaceView$EglHelper.start (GLSurfaceView.java:1070)

 

at com.ansca.corona.graphics.opengl.GLSurfaceView$GLThread.guardedRun (GLSurfaceView.java:1508)

 

at com.ansca.corona.graphics.opengl.GLSurfaceView$GLThread.run (GLSurfaceView.java:1378)

 

 

Second Error

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

 

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** pid: 0, tid: 0 >>> com.gbeegames. <<< backtrace:

 

#00 pc 0000000000028c84 /system/lib/libc.so (dlfree+1239)

 

#01 pc 000000000000f2ab /system/lib/libc.so (free+10)

 

#02 pc 000000000009390c /data/app/com.gbeegames.stellartrek-2/lib/arm/libcorona.so

 

#03 pc 000000000012dfac /data/app/com.gbeegames.stellartrek-2/lib/arm/libcorona.so

 

#04 pc 000000000008a16c /data/app/com.gbeegames.stellartrek-2/lib/arm/libcorona.so

 

#05 pc 0000000000088b2c /data/app/com.gbeegames.stellartrek-2/lib/arm/libcorona.so

 

#06 pc 000000000002c010 /data/app/com.gbeegames.stellartrek-2/lib/arm/libcorona.so

 

#07 pc 000000000002f3c4 /data/app/com.gbeegames.stellartrek-2/lib/arm/libcorona.so (Java_com_ansca_corona_JavaToNativeShim_nativeDone+28)

 

#08 pc 000000000046e2b5 /data/dalvik-cache/arm/data@app@com.gbeegames.stellartrek-2@base.apk@classes.dex

#2

These two are a killer for me because they push me over the bad behaviour threshold.

I have been getting them for a long time, since version …2017.3162  and in these versions: .3184, .3294, .3306, .3381

Any help greatly appreciated.

#3

I also get just one ANR that seems to hang around regardless of the version of Corona:

Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 47. Wait queue head age: 5507.8ms.)

“main” prio=5 tid=1 Runnable

| group=“main” sCount=0 dsCount=0 obj=0x74378390 self=0xb82a8290 | sysTid=9371 nice=-4 cgrp=default sched=0/0 handle=0xb6f4ac00 | state=R schedstat=( 0 0 0 ) utm=1062 stm=362 core=2 HZ=100 | stack=0xbe0e4000-0xbe0e6000 stackSize=8MB | held mutexes= “mutator lock”(shared held)

 

at java.lang.ThreadLocal.get (ThreadLocal.java:59)

 

at android.os.Looper.myLooper (Looper.java:174)

 

at android.view.Choreographer.isRunningOnLooperThreadLocked (Choreographer.java:709)

 

at android.view.Choreographer.scheduleFrameLocked (Choreographer.java:529)

 

at android.view.Choreographer.postCallbackDelayedInternal (Choreographer.java:374)

  • locked <0x0000bf86> (a java.lang.Object)

 

at android.view.Choreographer.postCallbackDelayed (Choreographer.java:357)

 

at android.view.Choreographer.postCallback (Choreographer.java:331)

 

at android.view.ViewRootImpl.scheduleConsumeBatchedInput (ViewRootImpl.java:5971)

 

at android.view.ViewRootImpl$WindowInputEventReceiver.onBatchedInputEventPending (ViewRootImpl.java:6033)

 

at android.view.InputEventReceiver.dispatchBatchedInputEventPending (InputEventReceiver.java:191)

 

at android.os.MessageQueue.nativePollOnce (Native method)

 

at android.os.MessageQueue.next (MessageQueue.java:323)

 

at android.os.Looper.loop (Looper.java:135)

 

at android.app.ActivityThread.main (ActivityThread.java:5452)

 

at java.lang.reflect.Method.invoke! (Native method)

 

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:762)

 

at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:652)

Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 47. Wait queue head age: 5507.8ms.)

#4

I’ve shared this with Engineering. They may be able to make sense of this.

Rob

#5

The first bug has been probably fixed by the corona devs, I’ve been getting a lot of them since june, but after building the app with corona version 3381, the errors are gone.

Looks like it was mainly an issue with new Huawei phones:

fDGEmy7.png

#6

Input dispatching timed out  - I get hundreds of these a day.  Wish this would get fixed.

#7

"Waiting to send non-key event because the touched window has not finished"

I also have a huge number of these errors, so most likely it is common error for the corona SDK!

#8

These two are a killer for me because they push me over the bad behaviour threshold.

I have been getting them for a long time, since version …2017.3162  and in these versions: .3184, .3294, .3306, .3381

Any help greatly appreciated.

#9

I also get just one ANR that seems to hang around regardless of the version of Corona:

Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 47. Wait queue head age: 5507.8ms.)

“main” prio=5 tid=1 Runnable

| group=“main” sCount=0 dsCount=0 obj=0x74378390 self=0xb82a8290 | sysTid=9371 nice=-4 cgrp=default sched=0/0 handle=0xb6f4ac00 | state=R schedstat=( 0 0 0 ) utm=1062 stm=362 core=2 HZ=100 | stack=0xbe0e4000-0xbe0e6000 stackSize=8MB | held mutexes= “mutator lock”(shared held)

 

at java.lang.ThreadLocal.get (ThreadLocal.java:59)

 

at android.os.Looper.myLooper (Looper.java:174)

 

at android.view.Choreographer.isRunningOnLooperThreadLocked (Choreographer.java:709)

 

at android.view.Choreographer.scheduleFrameLocked (Choreographer.java:529)

 

at android.view.Choreographer.postCallbackDelayedInternal (Choreographer.java:374)

  • locked <0x0000bf86> (a java.lang.Object)

 

at android.view.Choreographer.postCallbackDelayed (Choreographer.java:357)

 

at android.view.Choreographer.postCallback (Choreographer.java:331)

 

at android.view.ViewRootImpl.scheduleConsumeBatchedInput (ViewRootImpl.java:5971)

 

at android.view.ViewRootImpl$WindowInputEventReceiver.onBatchedInputEventPending (ViewRootImpl.java:6033)

 

at android.view.InputEventReceiver.dispatchBatchedInputEventPending (InputEventReceiver.java:191)

 

at android.os.MessageQueue.nativePollOnce (Native method)

 

at android.os.MessageQueue.next (MessageQueue.java:323)

 

at android.os.Looper.loop (Looper.java:135)

 

at android.app.ActivityThread.main (ActivityThread.java:5452)

 

at java.lang.reflect.Method.invoke! (Native method)

 

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:762)

 

at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:652)

Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 47. Wait queue head age: 5507.8ms.)

#10

I’ve shared this with Engineering. They may be able to make sense of this.

Rob

#11

The first bug has been probably fixed by the corona devs, I’ve been getting a lot of them since june, but after building the app with corona version 3381, the errors are gone.

Looks like it was mainly an issue with new Huawei phones:

fDGEmy7.png

#12

Input dispatching timed out  - I get hundreds of these a day.  Wish this would get fixed.

#13

"Waiting to send non-key event because the touched window has not finished"

I also have a huge number of these errors, so most likely it is common error for the corona SDK!