-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes in native code #2315
Comments
I'll see if I can translate any of these backtraces into code locations using ndk-stack. Are these crashes all using tangram-es 0.17.1? Your suggestion about providing debug symbols with releases makes sense to me, if it isn't terribly complicated. It seems like Google Play is able to symbolicate native crash stack traces if you upload a symbols file with the app. So I'll test whether an Android library like tangram-es is able to produce symbols in a way that an app can upload. |
Yes, except the last one (so far) |
Yes, exactly. I actually get warnings every time I upload a new release that the app contains native libraries and that it would be advisable to upload debug symbols to be able to make sense of the stack traces. A quick search in the docs reveal that this might be as easy as adding one property to the Obviously didn't test it, so far I stayed cleared from any NDK stuff, so I have no knowledge in this. |
There have been a number of crashes in native tangram code. These don't appear that often, about 1.5% of user sessions are affected by any of those. I have no more information about this, because (I think) it never occured to me.
However, I am not sure if these backtraces are helpful at all. The addresses after
# 00 pc
are consistent across different devices and crash reports though.There seem to be various issues and it varies how often each happen.
If they are not useful like this, is there something that can be done to make (future) backtraces more useful? E.g. would it be possible to release debug symbols or something together with each release?
signal 7 (SIGBUS), code 1 (BUS_ADRALN)
Happened so far on
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
Happened so far on
Same as above but addresses in first few lines are different
signal 4 (SIGILL), code 1 (ILL_ILLOPC)
Happened so far on
Same as above but addresses in first few lines are different
Same as above but addresses in first few lines are different
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR)
Happened so far on
Same as above but addresses in first few lines are different
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
Happened so far on:
The text was updated successfully, but these errors were encountered: