-
Notifications
You must be signed in to change notification settings - Fork 21
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
App Crash with YOLO11n TFLite Model on Android. Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) on GPU mode #555
Comments
Hi @emoo44566, Your Yolov11 project is empty -- are you testing it in one of the other projects? |
Hi The code for YOLOv11 should work similarly—just replace or add the YOLOv11 model to this project. Let me know if you need any help with the process! |
Hi @emoo44566, I'm yielding these results with the
It actually doesn't crash for me as it seems to fallback to the XNNPack Delegate I am using a Pixel 8 Pro API 34-ext12 ARM emulator... which phone(s) are you using? |
The crash only happens on certain phones, such as some Xiaomi devices. |
Original Issue: App Crash with YOLO11n TFLite Model on Android. Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) on GPU mode
Original Author: @emoo44566
Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf 2.16.1
Custom code
Yes
OS platform and distribution
Android
Mobile device
Some Android Devices
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I converted the YOLO11n model to TensorFlow Lite (TFLite) and used it in my Android app. However, my app crashes on some Android devices, and the following error appears in Logcat:
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
To create the TFLite model, I tried various conversion options in YOLO, as shown below:
Despite testing different configurations, the app consistently crashes when using the model in GPU mode.
Interestingly, this issue only occurs with the YOLO11n TFLite model. When I use other TFLite models, such as YOLOv8n or YOLOv9t, everything works fine. This suggests there may be a compatibility issue or a bug in the TFLite Android library specific to the YOLO11n model.
Standalone code to reproduce the issue
Relevant log output
No response
The text was updated successfully, but these errors were encountered: