-
Notifications
You must be signed in to change notification settings - Fork 24.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
Android Crash Thread: SIGQUIT 0x0000000000000000 #43541
Comments
|
|
It seems to be an out of memory issue be careful to set |
I'm unsure how are we supposed to help without a reproducer |
Cortinico, thank you for replying and I can see your point. Currently we have just added this field in AndroidManifest.xml and will continue to monitor this issue after next release.
|
having same issue on samsung device with |
same problem on samsung devices after upgrade 75.2, |
Description
Crashed: Thread: SIGQUIT 0x0000000000000000.
#00 pc 0x1edb0 libc.so (BuildId: 50fe11b9d556e088ce72bbd1db5f587d).
#01 pc 0xb1024 libart.so (BuildId: f1e2925e801d2071a5c2bd7ea55a67a1).
#02 pc 0x39afe4 libart.so (BuildId: f1e2925e801d2071a5c2bd7ea55a67a1)
React Native Version: 0.71.11 with Hermes enabled
After investigating the statistics in Firebase Crashlytics, I found
This crash seems a lot like #33083 which has been closed.
Steps to reproduce
This issue has 509 crash events affecting 315 users in last 30 days according to Firebase Crashlytics.
Unfortunately, there is currently no obvious method found to reproduce this crash issue, we are trying to find one.
React Native Version
0.71.11
Affected Platforms
Runtime - Android
Output of
npx react-native info
Stacktrace or Logs
Reproducer
null
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: