Frequent Android Crashes

Solar2D Android
#121

not to muddy the waters, but with regard to ANR’s not crashes, the following one is my  prime  offender (having 181 reports, next biggest having only 17 reports, then just various onesy-twosy reports below that), I mention it in this context primarily because libopenal/libalmixer are again present near the top: 

EDIT:  build 2017.3155

executing service com.dev.app/shared.google.play.services.base.PackageStateChangedService (no location available) "main" prio=5 tid=1 Native | group="main" sCount=1 dsCount=0 obj=0x75f11718 self=0xe7305400 | sysTid=20465 nice=-4 cgrp=default sched=0/0 handle=0xea93e534 | state=S schedstat=( 0 0 0 ) utm=387 stm=160 core=4 HZ=100 | stack=0xff662000-0xff664000 stackSize=8MB | held mutexes= native: pc 0000000000017520 /system/lib/libc.so (syscall+28) native: pc 00000000000477bf /system/lib/libc.so (pthread\_join+146) native: pc 0000000000015b58 /data/app/com.dev.app-2/lib/arm/libopenal.so (alcDestroyContext+516) native: pc 0000000000008ed7 /data/app/com.dev.app-2/lib/arm/libalmixer.so (ALmixer\_Quit+230) native: pc 000000000011d48c /data/app/com.dev.app-2/lib/arm/libcorona.so (???) native: pc 000000000011f8c0 /data/app/com.dev.app-2/lib/arm/libcorona.so (???) native: pc 000000000012f9b4 /data/app/com.dev.app-2/lib/arm/libcorona.so (???) native: pc 000000000002b6fc /data/app/com.dev.app-2/lib/arm/libcorona.so (???) native: pc 000000000002e9f8 /data/app/com.dev.app-2/lib/arm/libcorona.so (Java\_com\_ansca\_corona\_JavaToNativeShim\_nativeDone+28) native: pc 00000000000317a5 /data/app/com.dev.app-2/oat/arm/base.odex (Java\_com\_ansca\_corona\_JavaToNativeShim\_nativeDone\_\_J+80) at com.ansca.corona.JavaToNativeShim.nativeDone (Native method) at com.ansca.corona.JavaToNativeShim.destroy (JavaToNativeShim.java:277) at com.ansca.corona.Controller.destroy (Controller.java:286) - locked \<0x0f6a25ca\> (a com.ansca.corona.Controller) at com.ansca.corona.CoronaRuntime.dispose (CoronaRuntime.java:88) at com.ansca.corona.CoronaActivity.onDestroy (CoronaActivity.java:1698) at android.app.Activity.performDestroy (Activity.java:7195) at android.app.Instrumentation.callActivityOnDestroy (Instrumentation.java:1161) at android.app.ActivityThread.performDestroyActivity (ActivityThread.java:4573) at android.app.ActivityThread.handleDestroyActivity (ActivityThread.java:4609) at android.app.ActivityThread.-wrap7 (ActivityThread.java) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1692) at android.os.Handler.dispatchMessage (Handler.java:102) at android.os.Looper.loop (Looper.java:154) at android.app.ActivityThread.main (ActivityThread.java:6682) at java.lang.reflect.Method.invoke! (Native method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1520) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1410)
#122

Sounds “dangerous” to me!

#123

@SGS

Well. It isn’t.

@davebollinger

Build number, please. (it is better if you edit your post and add build number to it)

#124

* This one affects almost all of my apps. Seems to be restricted to android versions from 7.0 and newer. Corona version somewhere between 2017.3114 - 2017.3157

signal 5 (SIGTRAP), code 1 (TRAP_BRKPT) backtrace: native: pc 00000000004cd104 /data/app/com.android.chrome-1/base.apk

Any news on this one?

I am seeing this also a lot on version 7 and above.

Best regards,

Bjoern

#125

After a week (not really enough time, but…) on the 3169 build I’ve not yet seen the zn7*bitmap crash.  Not conclusive, just reporting.  FWIW, the things that have shown up so far are:

Build 2017.2169, #1 crash after a week: java.lang.UnsatisfiedLinkError: at java.lang.Runtime.loadLibrary (Runtime.java:367) at java.lang.System.loadLibrary (System.java:1076) at com.ansca.corona.JavaToNativeShim.\<clinit\> (JavaToNativeShim.java:115) at com.ansca.corona.CoronaEnvironment.setLuaErrorHandler (CoronaEnvironment.java:391) at com.ansca.corona.CoronaEnvironment.\<clinit\> (CoronaEnvironment.java:50) at com.ansca.corona.CoronaActivity.onCreate (CoronaActivity.java:230) at android.app.Activity.performCreate (Activity.java:6309) at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1113) at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2519) at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2654) at android.app.ActivityThread.-wrap11 (ActivityThread.java) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1488) at android.os.Handler.dispatchMessage (Handler.java:111) at android.os.Looper.loop (Looper.java:207) at android.app.ActivityThread.main (ActivityThread.java:5728) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:789) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:679)

Build 2017.2169, #1 ANR after a week: Broadcast of Intent { act=android.intent.action.SCREEN\_OFF flg=0x50000010 VirtualScreenParam=Params{mDisplayId=-1, null, mFlags=0x00000000)} (has extras) } (no location available) "main" tid=1 Native "main" prio=5 tid=1 Native | group="main" sCount=1 dsCount=0 obj=0x76f18530 self=0xf4bf6500 | sysTid=9830 nice=-4 cgrp=default sched=0/0 handle=0xf72efd54 | state=S schedstat=( 0 0 0 ) utm=136 stm=88 core=2 HZ=100 | stack=0xff079000-0xff07b000 stackSize=8MB | held mutexes= native: pc 0000000000017694 /system/lib/libc.so (syscall+28) native: pc 000000000004016d /system/lib/libc.so (pthread\_join+124) native: pc 0000000000015b58 /data/app/com.dev.app-1/lib/arm/libopenal.so (alcDestroyContext+516) native: pc 0000000000008ed7 /data/app/com.dev.app-1/lib/arm/libalmixer.so (ALmixer\_Quit+230) native: pc 000000000011d53c /data/app/com.dev.app-1/lib/arm/libcorona.so (???) native: pc 000000000011f970 /data/app/com.dev.app-1/lib/arm/libcorona.so (???) native: pc 000000000012fa64 /data/app/com.dev.app-1/lib/arm/libcorona.so (???) native: pc 000000000002b6fc /data/app/com.dev.app-1/lib/arm/libcorona.so (???) native: pc 000000000002e9f8 /data/app/com.dev.app-1/lib/arm/libcorona.so (Java\_com\_ansca\_corona\_JavaToNativeShim\_nativeDone+28) native: pc 00000000001e367d /data/app/com.dev.app-1/oat/arm/base.odex (Java\_com\_ansca\_corona\_JavaToNativeShim\_nativeDone\_\_J+80) at com.ansca.corona.JavaToNativeShim.nativeDone (Native method) at com.ansca.corona.JavaToNativeShim.destroy (JavaToNativeShim.java:277) at com.ansca.corona.Controller.destroy (Controller.java:286) - locked \<0x04db8245\> (a com.ansca.corona.Controller) at com.ansca.corona.CoronaRuntime.dispose (CoronaRuntime.java:88) at com.ansca.corona.CoronaActivity.onDestroy (CoronaActivity.java:1732) at android.app.Activity.performDestroy (Activity.java:7103) at android.app.Instrumentation.callActivityOnDestroy (Instrumentation.java:1171) at android.app.ActivityThread.performDestroyActivity (ActivityThread.java:5045) at android.app.ActivityThread.handleDestroyActivity (ActivityThread.java:5090) at android.app.ActivityThread.access$1700 (ActivityThread.java:222) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1855) at android.os.Handler.dispatchMessage (Handler.java:102) at android.os.Looper.loop (Looper.java:158) at android.app.ActivityThread.main (ActivityThread.java:7230) at java.lang.reflect.Method.invoke! (Native method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1230) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1120)

both occur on a variety of devices and os versions, no obvious patterns there.

#126

@Rob: Thank you for the info.

I have another report here, same plugins being used, and Corona build 3281: Not sure how informative this error is, but that’s the gist of it.

This one is listed under both ANR & Crash Reports:

 

#00 pc 00000000007adf74 /data/app/com.android.chrome-2/base.apk

 

#01 pc 0000000000048681 /system/lib/libc.so (pthread_detach+4)

 

#02 pc 00000000007ac4cd /data/app/com.android.chrome-2/base.apk

#127

Is there any more? That’s not much to go on.

Rob

#128

Reporting back on bitmap crash after a week+, it seems to be fix with 3169. Cheers @vlads.

#129

[member=‘Fungrip’], thank you for kind words! I’m really glad to hear that it helped.

Another good news: it seems, we have tracked down and fixed, at least some probably most, of OpenAL related crashes in 3175.

[member=‘Sphere Game Studios’], [member=‘davebollinger’] and [member=‘Yoger Games’]. You all reported OpenAL related crashes as being on top of your lists. When making next release, please, use 3175 or later to see if your issues was fixed (or, at least decreased in relative numbers).

Cheers!

#130

btw, kind words from me too re the bitmap crash (i wasn’t sure my results were “conclusive enough” yet to get too excited)

but this:  “we have tracked down and fixed, at least some probably most, of OpenAL related crashes in 3175.”

… has me jumping for joy even before trying it!  Even just the possibility that it’s finally resolved (it has haunted me long before google started penalizing for it) is a big deal.  I’ll definitely incorporate and test with next build/release, thanks!

#131

@Rob: Unfortunately, that is the only info we got from that error, which was semi-frequent in nature.

#132

Hey @vlad thanks for that… I will be pushing a build for one of my games tonight so I’ll feedback soon!

#133

It seems that the chrome crashes are caused by admob.

https://groups.google.com/forum/#!topic/google-admob-ads-sdk/I6giN0VbVa0

Thankfully, there is a crash log posted.

#134

Why are all the latest updates for HTML5?  Is there a large audience for it?   All I want is to be able to have a stable Android version.   HTML5 can go fly a kite :slight_smile:

#135

Most of the Android crash issues are plugin related because of problems in Google’s base SDK’s. Plugin updates don’t show up in daily build release notes unfortunately.  There are notes about back button crashes being fixed. Hopefully you will see more updates in a couple of days.

HTML5 opens the door for Facebook Instant Games and is highly desirable. Some people don’t see any value in it, others think it’s the most important thing we can offer.

Rob

#136

Thanks for the info Rob, you guys know your business model.   Glad to hear that the Android problems are getting dealt with, I understand now that the bug fixes are kind of hidden, I’m getting ansi (joke) to get my new updates and game out. 

Greg

#137

Greg, are there specific errors you are seeing?

Rob

#138

@vlads, thanks for the openAL fix. Very much appreciated.

Unfortunately, I do have to report that your fix might have introduced a new issue. Using build 3175, I now get the following error messages in the console: 

17dTesting Error with clearing buffer from source: Invalid OperationWarning: audio error: Failed to clear buffer from source: Invalid Operation

and

Warning: audio error: Could not bind data to source: Invalid Operation

These errors/warnings are appearing in an intensive audio scene where a lot of fireworks are launching and exploding (so, a lot of launch sounds and explosion sounds). Now, if these errors/warnings are just warnings and caught exceptions and will NOT cause the app to crash on a device, then I am OK with that. (If one in 7 fireworks don’t go boom, I can live with that). However, if these issues will generally crash the app on the device, then it becomes a serious problem for me. Any insights on this issue?

Thanks

Luay

EDIT: I just re-tested the app with build 3169, and, to my horror, these errors appeared. So, it seems these errors have nothing to do with your fix. Are they the initial reason for all these crash reports in openAL? I have no idea.

#139

@Rob: Was there an additional update for the back button crash fix, or was this the one that was done over a week ago? thanks

#140

Hi Rob,

Here are a few of my ANR’s/Crashes (I hope you don’t mind jpg’s)