-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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 crashes due to internal Webkit error #11790
Comments
The minimal MobX code is very minimal, basically adding this to root component:
Also, more information at mobxjs/mobx#734 |
Also, some sample callstack:
|
Did you see this error with Android dev mode on? Can you reproduce it with it turned off? If not, I have the feeling that this crash is caused by the same thing we found out in #11804. |
@AlbertBrand yes, I can reproduce it with both dev on and off. With dev being off, the problem is harder to reproduce - it requires larger arrays. My test project stopped crashing with dev=false, but when I made the array 10x longer and started access indices like 10k instead of 1000, it crashed again. |
Could you check if the fix in #11804 has any influence on how fast it crashes in dev mode? My hypothesis is that with the patch it should crash as often as without dev mode turned on. |
@AlbertBrand it still crashes |
+1 |
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. |
On
I'm not using mobx, so I'm not sure if this is the same issue of course. |
I'm also seeing this issue in production on RN 0.47.2 and I'm not using mobx either. The issue was seen on a Google Pixel XL 2 running Android 8.0. |
+1 Same issue after following the react publish guide to the letter. Seen on galaxy s8 running 8.0 as well |
Hi, same issue in production with RN 0.45.1 and i'm not using mobx. According to developer console ANR information issue was seen on device: @hramos can you guide us how to bring attention to this issue? Should we open a new ticket or something else? Thanks.
|
Hi, same issue in production with RN 0.50.3 and i'm not using mobx. According to developer console ANR information issue was seen on device: Samsung Galaxy Note8 (greatlte), 6144MB RAM, Android 7.1 pid: 0, tid: 0 >>> com.app <<< backtrace: |
I've got 50 and more of those daily
They are split in multiple clusters:
and many more At some time I read that this is a memory issue |
I'm creating some application with MobX and ReactNative. It crashes on Android within Webkit internals. I created minimal example to showcase it: https://github.com/IDTLabs/RNCrashTest - more info in its readme.
TL;DR: embedded webkit's JS VM doesn't handle well MobX observable arrays and crashes.
Reproduction
Sample project: https://github.com/IDTLabs/RNCrashTest
Solution
I believe that bumping Webkit from mid-2014 version to something newer will do the trick. This is not verified, though.
Additional Information
The text was updated successfully, but these errors were encountered: