-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Crash in libcamera2ndk.so (SIGSEGV) in versions prior to Android 8.1 / Android O MR1 (API 27) #291
Comments
This, unfortunately, is a known issue in Android versions prior to 8.1. It generally occurs only during extremely high CPU usage. There's nothing we can do about it. |
Any update concerning this problem ? Note that according to my Android Vitals dashboard, this crash happens almost only on: Galaxy S7 Edge (hero2lte) (47.3% of the crashes), Galaxy S7 (herolte) (42% of the crashes), Galaxy S7 (heroltebmc) (2.2% of the crashes) => 90% of the occurences of this crash happen on S7 (running Android 7.x). Do you plan to fix this problem ? The S7 represents 20% of my installs and thus crash has a bad influence on my rating. |
This issue happens with high CPU load resulting in blocked Binder threads. If you can reduce your app's CPU usage and avoid blocking/waiting in any callbacks running on Binder threads, it may reduce this issue. Long term, we're looking at ways to mitigate this issue, but they are major rewrites of substantial parts of our codebase. This is a bug in the android NDK Camera 2 API implementation that was fixed in Android 8.1. |
"avoid blocking/waiting in any callbacks running on Binder threads" : how to do that ? :) |
Anything related to Android services should avoid blocking in callbacks. Google Play Services for example. |
@RegisAG - try newest ARCore 1.9.0 - I have not experienced the freeze yet from time I've updated SDK and hopefully it stays this way :) Let me know if 1.9.0 ever crashes for you as it did in previous versions so I can be prepared that problem can still occur. |
We still experience this error in production. Only on Samsung devices (S8, A6, A7 2108) with Android versions 9 and 10. the stacktrace reads as follows:
Currently using ArCore 1.16 |
I have an app in production used by many users. On some of them, only on Android 7.x, I have got the following error:
Any idea on the origin of this problem ?
The text was updated successfully, but these errors were encountered: