Corona Team: lots of crash reports kitkat 4.4 ! Please help to analyse

guruk · December 29, 2014, 11:26am

Hi there,

i get lots (thousands) of crashreports in the last days from Android devices with firmware 4.4

I really dont know how to read them and where I could fix a problem.

It would be great could have a short look into and let me know what I could do.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: ‘lge/w5c_spr_us/w5c:4.4.2/KOT49I.LS620ZV3/LS620ZV3.1401441831:user/release-keys’
Revision: ‘6’
pid: 17203, tid: 17203, name: roid.mydaysfree >>> com.chris.android.mydaysfree <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
r0 fffffffc r1 00000000 r2 0000000a r3 00000050
r4 42323f4c r5 42323f48 r6 41c68a60 r7 000000a2
r8 00000008 r9 1dcd64ff sl 00000001 fp 03d09000
ip 00000001 sp bedfca08 lr 416ac19b pc 4008e0c8 cpsr 200b0010
d0 0000000000000000 d1 0000000000000000
d2 0000000000000000 d3 0000000000000000
d4 4058000000000000 d5 3ffacf1732c2fcb1
d6 3ff774df75c55d80 d7 402305555841ab47
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 0074006900760069 d17 006e0061004d0079
d18 0064007200610068 d19 0065007200610077
d20 007300690064002e d21 00790061006c0070
d22 006900440049002e d23 0061006c00700073
d24 3ff774df75c55d7f d25 400921fb54442d18
d26 bfaddec3293b31e4 d27 3fa97b8df0aa5469
d28 3f90ad3ae322da11 d29 3f86a4910476f2fe
d30 3fd5559e94e4de14 d31 bfc99a0b8ae3a712
scr 20000012

backtrace:
#00 pc 000210c8 /system/lib/libc.so (nanosleep+12)
#01 pc 00056197 /system/lib/libdvm.so (dvmLockObject+178)
#02 pc 00020d9c /system/lib/libdvm.so
#03 pc 00030ec8 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#04 pc 0002e560 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#05 pc 00063795 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
#06 pc 0004f88d /system/lib/libdvm.so
#07 pc 000505e9 /system/lib/libandroid_runtime.so
#08 pc 00086431 /system/lib/libandroid_runtime.so
#09 pc 000107cb /system/lib/libutils.so (android::Looper::pollInner(int)+478)
#10 pc 00010879 /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+92)
#11 pc 0006b3d9 /system/lib/libandroid_runtime.so (android::NativeMessageQueue::pollOnce(_JNIEnv*, int)+22)
#12 pc 000204cc /system/lib/libdvm.so (dvmPlatformInvoke+112)
#13 pc 000512af /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
#14 pc 00029960 /system/lib/libdvm.so
#15 pc 00030ec8 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#16 pc 0002e560 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#17 pc 00063a79 /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+392)
#18 pc 0006b943 /system/lib/libdvm.so
#19 pc 00029960 /system/lib/libdvm.so
#20 pc 00030ec8 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#21 pc 0002e560 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#22 pc 00063795 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
#23 pc 0004ce97 /system/lib/libdvm.so
#24 pc 0004df5f /system/lib/libandroid_runtime.so
#25 pc 0004ecb7 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+354)
#26 pc 0000109b /system/bin/app_process
#27 pc 0000e56b /system/lib/libc.so (__libc_init+50)
#28 pc 00000db0 /system/bin/app_process

>>>>>=============================================================

and even more thousands for

>>>>===========================================================

android.view.WindowManager$BadTokenException: Unable to add window – token android.os.BinderProxy@41bc2170 is not valid; is your activity running?

at android.view.ViewRootImpl.setView(ViewRootImpl.java:569)
at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:259)
at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69)
at android.app.Dialog.show(Dialog.java:296)
at com.ansca.corona.Controller$6.run(Controller.java:805)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5082)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:598)
at dalvik.system.NativeStart.main(Native Method)

>>>>>=============================================================

and even thousands (over ten of thousands) ANR Reports !!!

>>>>===========================================================

----- pid 4948 at 2014-12-29 11:40:06 -----
Cmd line: com.chris.android.mydaysfree

JNI: CheckJNI is off; workarounds are off; pins=0; globals=343

DALVIK THREADS:
(mutexes: tll=0 tsl=0 tscl=0 ghl=0)

“main” prio=5 tid=1 MONITOR
| group=“main” sCount=1 dsCount=0 obj=0x4189eea0 self=0x41799388
| sysTid=4948 nice=-11 sched=0/0 cgrp=apps handle=1074495828
| state=S schedstat=( 0 0 0 ) utm=49 stm=50 core=0
at com.ansca.corona.events.EventManager.addEvent(EventManager.java:~27)

waiting to lock <0x42acbd78> (a com.ansca.corona.events.EventManager) held by tid=10 (GLThread 478)
at com.ansca.corona.CoronaRuntimeTaskDispatcher.send(CoronaRuntimeTaskDispatcher.java:116)
at com.ansca.corona.graphics.opengl.CoronaGLSurfaceView.sendOrientationChangedEvent(CoronaGLSurfaceView.java:185)
at com.ansca.corona.graphics.opengl.CoronaGLSurfaceView.access$400(CoronaGLSurfaceView.java:5)
at com.ansca.corona.graphics.opengl.CoronaGLSurfaceView$2.onOrientationChanged(CoronaGLSurfaceView.java:116)
at android.view.OrientationEventListener$SensorEventListenerImpl.onSensorChanged(OrientationEventListener.java:143)
at android.hardware.SystemSensorManager$SensorEventQueue.dispatchSensorEvent(SystemSensorManager.java:474)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.next(MessageQueue.java:138)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:5356)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1265)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081)
at dalvik.system.NativeStart.main(Native Method)

“OkHttp ConnectionPool” daemon prio=5 tid=20 TIMED_WAIT
| group=“main” sCount=1 dsCount=0 obj=0x42bd1788 self=0x7bb22338
| sysTid=22174 nice=0 sched=0/0 cgrp=apps handle=2075273104
| state=S schedstat=( 0 0 0 ) utm=0 stm=0 core=0
at java.lang.Object.wait(Native Method)

waiting on <0x42bd1860> (a java.lang.VMThread) held by tid=20 (OkHttp ConnectionPool)
at java.lang.Thread.parkFor(Thread.java:1205)
at sun.misc.Unsafe.park(Unsafe.java:325)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:197)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2056)
at java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:435)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1035)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1097)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)

rob · December 29, 2014, 6:50pm

This shouldn’t have magically just started. Did you do an app update? If so, what changes did you make? Did you build with a different version of Corona SDK than what you previously built with?

If this magically just started without you doing updates, then it sounds like it may be something where your app is interacting with the network. Are you making any network type requests (be it network.request(), analytics, facebook, etc.)?

We need to narrow down what changed before I can go to an engineer with this.

Rob

guruk · December 29, 2014, 7:49pm

Thanks Rob,

I just can say that i got more and more reports over the last weeks, since Im on travel I couldnt look deeper into.

Today I checked the crashreports and see that the above CrashReports seem nearly only appear on Android 4.4 and higher.

Maybe 0.5% on lower Firwares.

The last App Update was already months ago.

As I do updates around each 1/2 year, for sure its different Corona SDKs used.

and yes, I do at the beginning of the Appstart a Network Request to my server for AdMediation. Also that was in the App since years and never made a problem.

As long its not a Google Report Problem this really just started since the last update of my App and mainly for Firmware above 4.4

Also for another app (not with Corona) i got several problems since 4.4 and it may problem with the Android Firmwares.

When I look for the Devices used, I also get the Feeling that a good amount of them are rooted with Gyanogen mod.

Thanks again for looking into it.

Im also willed to share my Source with you for sure. U may have more devices to test. On my latest Galaxy S4 / S5 and an older Nexus One it still works fine.

Attached a 2 Screenshots from the Google Dashboard about the last 24 Hours, Android version 4.4

(Kinda NO Reports at all for all lower Firmwares, also in increasing amount for Version 5.0, but with lower amount compared to devices with that installed Firmware)

U see its a HUGE Amount and I would be really glad u can help me to remove that, as I got for sure also lots of bad Comments.

Regards
Chris

rob · December 30, 2014, 5:23am

If your app hasn’t been updated in the last couple of months and these suddenly started, it’s not likely a Corona issue or a code issue on your part. Something likely changed on a service that you’re talking to and your app is now getting data it doesn’t know how to handle (or possibly corrupting a network.request call).

If it’s rooted devices, we can’t even being to try and support that. But if this is happening on stock devices and you can provide a test case where the data you are receiving is causing the app to crash, then we might be able to get engineering to look at this.

Rob

guruk · December 30, 2014, 12:02pm

it started with android 4.4 maybe there is a small incompatibility with the api and 4.4 i dont know

the talk via network request is also still the same.

also i looked again more in detail and can say its around 50:50 unrooted / rooted device . so more than enough stock devices

I could just ask YOU to download my app
https://play.google.com/store/apps/details?id=com.chris.android.mydaysfree&hl=en

and do a test on some different devices if it also crash, … seems always while app start itself (that would make sense as i do the network requests at that point also)

as said i got 10.000 tsnds of Reports but on my own device it works fine :!)*(

roaminggamer · December 30, 2014, 4:40pm

@Guruk,

Hi. I’m chiming in because I seem to remember someone in the community releasing a utility which would produce more detailed crash reports, thus giving you a better chance of zooming in on the issue.

@All,

I’m away from my office so I can’t look through my list of ‘great sounding resources’. I’ll look at it when I get back. However, if anyone reading this remembers this resource and has a link to it, please post here to help ‘guruk’.

guruk · December 30, 2014, 11:05pm

oh, that would be so amazing… some simple crash report a mortal person can read easily and best with a hint where to start fixing

happy new year

roaminggamer · December 31, 2014, 2:44am

here it is: http://forums.coronalabs.com/topic/50004-corona-advanced-logging/

rob · December 29, 2014, 6:50pm