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
My app crashed in Android emulator 7.0 #13668
Comments
I had the same problem it crases on Android 7.0. From a production app. I got this error message on google play console
I had the same version of react-native, this could be related. I'm not sure. Android 6.0 works fine tho. |
I have an app in production and can confirm that Android 7.0 seems to have some issue with React Native, ~60% of our crashes are happening there. Need to investigate more, this issue seems a good thread to work around it. |
+1 on emulator |
3 similar comments
+1 on emulator |
+1 on emulator |
+1 on emulator |
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally! If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution. |
Description
1.Explain what you did
My project is a standard React Native project created using react-native init.
, then I used react-native run-android.
2.What you expected to happen
Android emulator should display normal view.
3.What actually happens
However,My app crashed。(but my real phone is ok)
react-native 0.43
react 16.0.0-alpha.6
Android emulator android 7.0
Real phone android 5.1.1
Reproduction Steps and Sample Code
`04-26 11:27:13.022 7991-7991/? I/art: Not late-enabling -Xcheck:jni (already on)
04-26 11:27:13.023 7991-7991/com.tjhms W/art: Unexpected CPU variant for X86 using defaults: x86
04-26 11:27:13.207 7991-7991/com.tjhms V/fb-UnpackingSoSource: locked dso store /data/user/0/com.tjhms/lib-main
04-26 11:27:13.221 7991-7991/com.tjhms I/fb-UnpackingSoSource: dso store is up-to-date: /data/user/0/com.tjhms/lib-main
04-26 11:27:13.221 7991-7991/com.tjhms V/fb-UnpackingSoSource: releasing dso store lock for /data/user/0/com.tjhms/lib-main
04-26 11:27:13.277 7991-7991/com.tjhms D/NetworkSecurityConfig: No Network Security Config specified, using platform default
04-26 11:27:13.800 7991-8017/com.tjhms I/OpenGLRenderer: Initialized EGL, version 1.4
04-26 11:27:13.800 7991-8017/com.tjhms D/OpenGLRenderer: Swap behavior 1
04-26 11:27:13.801 7991-8017/com.tjhms W/OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
04-26 11:27:13.801 7991-8017/com.tjhms D/OpenGLRenderer: Swap behavior 0
04-26 11:27:13.838 7991-8017/com.tjhms E/gralloc_ranchu: gralloc_register_buffer(0xe8a5a3c0): invalid buffer
04-26 11:27:13.838 7991-8017/com.tjhms W/GraphicBufferMapper: registerBuffer(0xe8a5a3c0) failed -22 (Invalid argument)
04-26 11:27:13.838 7991-8017/com.tjhms E/GraphicBuffer: unflatten: registerBuffer failed: Invalid argument (-22)
04-26 11:27:13.838 7991-8017/com.tjhms E/Surface: dequeueBuffer: IGraphicBufferProducer::requestBuffer failed: -22
04-26 11:27:13.838 7991-8017/com.tjhms E/EGL_emulation: tid 8017: init(324): error 0x3003 (EGL_BAD_ALLOC)
04-26 11:27:13.839 7991-8017/com.tjhms E/EGL_emulation: tid 8017: eglCreateWindowSurface(847): error 0x3003 (EGL_BAD_ALLOC)
04-26 11:27:13.843 7991-8017/com.tjhms A/OpenGLRenderer: Failed to create EGLSurface for window 0xdb3d8508, eglErr = EGL_BAD_ALLOC
04-26 11:27:13.846 7991-8017/com.tjhms A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 8017 (RenderThread)
Solution
What needs to be done to address this issue? Ideally, provide a pull request with a fix.
Additional Information
The text was updated successfully, but these errors were encountered: