You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating from react-native v0.66.4 --> 0.66.5 results in a runtime v8 crash in our app, with react-native-v8@0.66.4-patch.0.
As a solution I have tried updating react-native-v8 to v1.5.2 (we were using react-native@0.66.4-patch.0) but v1.5.2 does not seem to be working, reported in #149.
Unfortunately a bare bones app with the same react-native and react-native-v8 versions does not crash. However I can share the app code that is resulting in this crash: digidem/mapeo-mobile#1040 — this was working before with react-native@0.66.4, however we are no longer able to test that or revert to it because Facebook broke all react-native builds
Error log (from adb log "*:E"):
11-07 13:14:19.023 17803 17862 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x109 in tid 17862 (mqt_js), pid 17803 (com.mapeo.debug)
11-07 13:14:19.063 17872 17872 E crash_dump32: failed to interrupt 17873 to detach: No such process
11-07 13:14:19.080 17872 17872 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-07 13:14:19.080 17872 17872 F DEBUG : Build fingerprint: 'Android/sdk_phone_x86/generic_x86:9/PSR1.180720.012/4923214:userdebug/test-keys'
11-07 13:14:19.080 17872 17872 F DEBUG : Revision: '0'
11-07 13:14:19.080 17872 17872 F DEBUG : ABI: 'x86'
11-07 13:14:19.080 17872 17872 F DEBUG : pid: 17803, tid: 17862, name: mqt_js >>> com.mapeo.debug <<<
11-07 13:14:19.080 17872 17872 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x109
11-07 13:14:19.080 17872 17872 F DEBUG : Cause: null pointer dereference
11-07 13:14:19.080 17872 17872 F DEBUG : eax 00000104 ebx c787c788 ecx 0000003e edx 47fc5481
11-07 13:14:19.080 17872 17872 F DEBUG : edi c787c838 esi c22d0ea0
11-07 13:14:19.080 17872 17872 F DEBUG : ebp c787c778 esp c787c730 eip c880101e
11-07 13:14:19.084 17872 17872 F DEBUG :
11-07 13:14:19.084 17872 17872 F DEBUG : backtrace:
11-07 13:14:19.084 17872 17872 F DEBUG : #00 pc 00ef501e /data/app/com.mapeo.debug-ZGCcIhvtNt9b-qjZhWkcog==/lib/x86/libv8android.so (v8::internal::LookupIterator::State v8::internal::LookupIterator::LookupInRegularHolder<false>(v8::internal::Map, v8::internal::JSReceiver)+446)
11-07 13:14:19.084 17872 17872 F DEBUG : #01 pc 00ef295f /data/app/com.mapeo.debug-ZGCcIhvtNt9b-qjZhWkcog==/lib/x86/libv8android.so (v8::internal::LookupIterator::State v8::internal::LookupIterator::LookupInSpecialHolder<false>(v8::internal::Map, v8::internal::JSReceiver)+351)
11-07 13:14:19.084 17872 17872 F DEBUG : #02 pc 00ef210e /data/app/com.mapeo.debug-ZGCcIhvtNt9b-qjZhWkcog==/lib/x86/libv8android.so (void v8::internal::LookupIterator::Start<false>()+142)
11-07 13:14:19.084 17872 17872 F DEBUG : #03 pc 01033d96 /data/app/com.mapeo.debug-ZGCcIhvtNt9b-qjZhWkcog==/lib/x86/libv8android.so (v8::internal::Runtime::GetObjectProperty(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, bool*)+470)
11-07 13:14:19.084 17872 17872 F DEBUG : #04 pc 0103a595 /data/app/com.mapeo.debug-ZGCcIhvtNt9b-qjZhWkcog==/lib/x86/libv8android.so
11-07 13:14:19.084 17872 17872 F DEBUG : #05 pc 00acd8f6 /data/app/com.mapeo.debug-ZGCcIhvtNt9b-qjZhWkcog==/lib/x86/libv8android.so
The text was updated successfully, but these errors were encountered:
Updating from react-native v0.66.4 --> 0.66.5 results in a runtime v8 crash in our app, with
react-native-v8@0.66.4-patch.0
.As a solution I have tried updating react-native-v8 to v1.5.2 (we were using react-native@0.66.4-patch.0) but v1.5.2 does not seem to be working, reported in #149.
Unfortunately a bare bones app with the same react-native and react-native-v8 versions does not crash. However I can share the app code that is resulting in this crash: digidem/mapeo-mobile#1040 — this was working before with react-native@0.66.4, however we are no longer able to test that or revert to it because Facebook broke all react-native builds
Error log (from
adb log "*:E"
):The text was updated successfully, but these errors were encountered: