signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41 (Android 8.0) #25494

ebaynaud · 2019-07-04T10:59:45Z

Same as #24261 but still occuring on device Caterpillar S41 (Android 8.0).

React Native version: 0.59.10

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.myapp <<<

backtrace:
  #00  pc 00000000000f7748  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #01  pc 0000000000143fe8  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #02  pc 000000000012f0a8  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #03  pc 0000000000139484  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #04  pc 000000000013900c  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #05  pc 00000000001fb9c4  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #06  pc 00000000001f8e90  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #07  pc 00000000001f96bc  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #08  pc 00000000001e41a0  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #09  pc 00000000006171ec  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #10  pc 0000000000617950  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #11  pc 000000000060de7c  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #12  pc 000000000061b084  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #13  pc 0000000000646dc8  /data/app/com.myapp-Fgc_pnA5bQP7DCgIn51TQQ==/lib/arm64/libjsc.so
  #14  pc 0000000000066f34  /system/lib64/libc.so (_ZL15__pthread_startPv+36)
  #15  pc 000000000001eb94  /system/lib64/libc.so (__start_thread+68)

The text was updated successfully, but these errors were encountered:

Kudo · 2019-07-04T12:14:21Z

@ebaynaud
Do you have any reproduced steps?
Otherwise, symbolicated backtrace would be helped.

wget https://registry.npmjs.org/jsc-android/-/jsc-android-245459.0.0.tgz
tar xf jsc-android-245459.0.0.tgz
unzip package/dist/org/webkit/android-jsc/r245459/android-jsc-r245459.aar

adb logcat -c
adb logcat | ndk-stack -sym jni/arm64-v8a/libjsc.so

ebaynaud · 2019-07-04T12:33:05Z

Sorry but no, I cannot reproduce by myself because I don't have this device within easy reach. The crash is coming from Google Play console.

thomasonweb · 2019-07-09T08:10:09Z

Hi Kudo,

I confirm crash is gone from Samsung devices but after upgrading to 0.59.10 we are still seeing it on a couple of other devices as well (unfortunately also through Google Play - I don't have access to such a device to reproduce).

So far I've seen it on:
Asus X555
Huawei P9 Lite
Huawei y6 2017
Huawei Y7 Prime 2018

Running Android 6.0, 7.0 and 8.0.

I've also seen a couple of devices running Android 9 or Android 8.1:
Huawei p smart 2019
Huawei p30

As you can see, Huawei devices are standing out. I have a Huawei P smart (FIG-LX1) running android 8.0 test device myself but it seems to be running just fine on that one.


pid: 0, tid: 0 >>> live.ablo <<<

backtrace:
#00 pc 00000000000f7748 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#1 pc 0000000000143fe8 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#2 pc 000000000012f0a8 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#3 pc 0000000000139484 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#4 pc 000000000013900c /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#5 pc 00000000001fb9c4 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#6 pc 00000000001f8e90 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#7 pc 00000000001f96bc /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#8 pc 00000000001e41a0 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#9 pc 00000000006171ec /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#10 pc 0000000000617950 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#11 pc 000000000060de7c /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#12 pc 000000000061b084 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#13 pc 0000000000646dc8 /data/app/com.myapp-7flUaqbvABD7Q-kusVtsLw==/lib/arm64/libjsc.so
#14 pc 0000000000082e10 /system/lib64/libc.so (__pthread_start(void*)+36)
#15 pc 0000000000024080 /system/lib64/libc.so (__start_thread+68)

xanderdeseyn · 2019-07-15T09:43:43Z

I'm experiencing it as well on a Huawei Y5 (2017).

jsaraiva · 2019-07-20T13:43:44Z

Same here. Asus ZenFone 3 Max, Android 8.1.
The stack trace (via Google Play Console) is almost exactly the same as the other ones in this issue (except for the pc for /system/lib64/libc.so, which would vary according to the device manufacturer or Android version, I guess).

pid: 0, tid: 0 >>> pt.geota.app <<<

backtrace:
  #00  pc 00000000000f7748  /data/data/pt.geota.app/lib-0/libjsc.so
  #01  pc 0000000000143fe8  /data/data/pt.geota.app/lib-0/libjsc.so
  #02  pc 000000000012f0a8  /data/data/pt.geota.app/lib-0/libjsc.so
  #03  pc 0000000000139484  /data/data/pt.geota.app/lib-0/libjsc.so
  #04  pc 000000000013900c  /data/data/pt.geota.app/lib-0/libjsc.so
  #05  pc 00000000001fb9c4  /data/data/pt.geota.app/lib-0/libjsc.so
  #06  pc 00000000001f8e90  /data/data/pt.geota.app/lib-0/libjsc.so
  #07  pc 00000000001f96bc  /data/data/pt.geota.app/lib-0/libjsc.so
  #08  pc 00000000001e41a0  /data/data/pt.geota.app/lib-0/libjsc.so
  #09  pc 00000000006171ec  /data/data/pt.geota.app/lib-0/libjsc.so
  #10  pc 0000000000617950  /data/data/pt.geota.app/lib-0/libjsc.so
  #11  pc 000000000060de7c  /data/data/pt.geota.app/lib-0/libjsc.so
  #12  pc 000000000061b084  /data/data/pt.geota.app/lib-0/libjsc.so
  #13  pc 0000000000646dc8  /data/data/pt.geota.app/lib-0/libjsc.so
  #14  pc 000000000007472c  /system/lib64/libc.so (__pthread_start(void*)+36)
  #15  pc 000000000001fbb4  /system/lib64/libc.so (__start_thread+68)

mars-lan · 2019-07-20T18:24:19Z

Seeing potentially similar issue for a variety of 64-bit phones running Android 9.
RN: 0.59.10
JSC: 241213.1.0 (with ICU i18n support)

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.invisatime <<<

backtrace:
  #00  pc 00000000004ae0c0  /data/data/com.invisatime/lib-0/libjsc.so
  #01  pc 00000000004ab608  /data/data/com.invisatime/lib-0/libjsc.so
  #02  pc 00000000004abd90  /data/data/com.invisatime/lib-0/libjsc.so
  #03  pc 0000000000498004  /data/data/com.invisatime/lib-0/libjsc.so
  #04  pc 000000000088ea1c  /data/data/com.invisatime/lib-0/libjsc.so
  #05  pc 000000000088f14c  /data/data/com.invisatime/lib-0/libjsc.so
  #06  pc 000000000088527c  /data/data/com.invisatime/lib-0/libjsc.so
  #07  pc 00000000008929f0  /data/data/com.invisatime/lib-0/libjsc.so
  #08  pc 00000000008a5098  /data/data/com.invisatime/lib-0/libjsc.so
  #09  pc 0000000000081938  /system/lib64/libc.so (__pthread_start(void*)+36)
  #10  pc 0000000000023478  /system/lib64/libc.so (__start_thread+68)

xanderdeseyn · 2019-07-23T12:21:25Z

I'm seeing this on at least 5 different devices. Anyone came up with a solution?

j-wang · 2019-07-23T20:56:35Z

@N1ghtly If you have the ability to do so, it might be worth trying to upgrade to 0.60.4 and turn Hermes on. See @Kudo's comment here:

#24261 (comment)

dhess-zynga · 2019-07-24T17:39:52Z

We're also seeing crashes on our build, w/ JSC r245459... @Kudo i attempted to symbolicate using your instructions from #25494 (comment), and here's what I came up with:

********** Crash dump: **********
pid: 0, tid: 0 >>> APPNAME <<<
Stack frame #00  pc 00000000000f7748  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::AccessCase::propagateTransitions(JSC::SlotVisitor&) const at sfp-exceptions.c:?
Stack frame #01  pc 0000000000143fe8  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::PolymorphicAccess::propagateTransitions(JSC::SlotVisitor&) const at sfp-exceptions.c:?
Stack frame #02  pc 000000000012f0a8  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::CodeBlock::propagateTransitions(JSC::ConcurrentJSLocker const&, JSC::SlotVisitor&) at sfp-exceptions.c:?
Stack frame #03  pc 0000000000139484  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::ExecutableToCodeBlockEdge::runConstraint(JSC::ConcurrentJSLocker const&, JSC::VM&, JSC::SlotVisitor&) at sfp-exceptions.c:?
Stack frame #04  pc 000000000013900c  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::ExecutableToCodeBlockEdge::visitChildren(JSC::JSCell*, JSC::SlotVisitor&) at sfp-exceptions.c:?
Stack frame #05  pc 00000000001fb9c4  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::SlotVisitor::drain(WTF::MonotonicTime)::$_3::operator()(JSC::MarkStackArray&) const at sfp-exceptions.c:?
Stack frame #06  pc 00000000001f8e90  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::SlotVisitor::drain(WTF::MonotonicTime) at sfp-exceptions.c:?
Stack frame #07  pc 00000000001f96bc  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine JSC::SlotVisitor::drainFromShared(JSC::SlotVisitor::SharedDrainMode, WTF::MonotonicTime) at sfp-exceptions.c:?
Stack frame #08  pc 00000000001e41a0  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine WTF::SharedTaskFunctor<void (), JSC::Heap::runBeginPhase(JSC::GCConductor)::$_17>::run() at sfp-exceptions.c:?
Stack frame #09  pc 00000000006171ec  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine WTF::ParallelHelperClient::runTask(WTF::RefPtr<WTF::SharedTask<void ()>, WTF::DumbPtrTraits<WTF::SharedTask<void ()> > > const&) at sfp-exceptions.c:?
Stack frame #10  pc 0000000000617950  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine WTF::ParallelHelperPool::Thread::work() at sfp-exceptions.c:?
Stack frame #11  pc 000000000060de7c  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine WTF::Function<void ()>::CallableWrapper<WTF::AutomaticThread::start(WTF::AbstractLocker const&)::$_0>::call() at sfp-exceptions.c:?
Stack frame #12  pc 000000000061b084  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*) at sfp-exceptions.c:?
Stack frame #13  pc 0000000000646dc8  /data/app/APPNAME-7N8FNwyuRgPc5XMrSr_hjQ==/lib/arm64/libjsc.so: Routine WTF::wtfThreadEntryPoint(void*) at sfp-exceptions.c:?
Stack frame #14  pc 0000000000069974  /system/lib64/libc.so (__pthread_start(void*)+36)
Stack frame #15  pc 000000000001f864  /system/lib64/libc.so (__start_thread+68)

mcuelenaere · 2019-07-25T09:47:01Z

We can confirm that the same issue occurs on beyondx (Samsung Galaxy S10 5G) on Android 9, which has an Exynos 9820 (ARMv8.2):

backtrace:
  #00  pc 00000000000f7748  /data/app/{APP_NAME}/lib/arm64/libjsc.so (JSC::AccessCase::propagateTransitions(JSC::SlotVisitor&) const+16)
  #01  pc 0000000000143fe8  /data/app/{APP_NAME}/lib/arm64/libjsc.so (JSC::PolymorphicAccess::propagateTransitions(JSC::SlotVisitor&) const+48)
  #02  pc 000000000012f0a8  /data/app/{APP_NAME}/lib/arm64/libjsc.so (JSC::CodeBlock::propagateTransitions(JSC::ConcurrentJSLocker const&, JSC::SlotVisitor&)+556)
  #03  pc 0000000000139484  /data/app/{APP_NAME}/lib/arm64/libjsc.so (JSC::ExecutableToCodeBlockEdge::runConstraint(JSC::ConcurrentJSLocker const&, JSC::VM&, JSC::SlotVisitor&)+40)
  #04  pc 000000000013900c  /data/app/{APP_NAME}/lib/arm64/libjsc.so (JSC::ExecutableToCodeBlockEdge::visitChildren(JSC::JSCell*, JSC::SlotVisitor&)+1044)
  #05  pc 00000000001fb9c4  /data/app/{APP_NAME}/lib/arm64/libjsc.so (_ZZN3JSC11SlotVisitor5drainEN3WTF13MonotonicTimeEENK3$_3clERNS_14MarkStackArrayE+324)
  #06  pc 00000000001f8e90  /data/app/{APP_NAME}/lib/arm64/libjsc.so (JSC::SlotVisitor::drain(WTF::MonotonicTime)+132)
  #07  pc 00000000001f96bc  /data/app/{APP_NAME}/lib/arm64/libjsc.so (JSC::SlotVisitor::drainFromShared(JSC::SlotVisitor::SharedDrainMode, WTF::MonotonicTime)+580)
  #08  pc 00000000001e41a0  /data/app/{APP_NAME}/lib/arm64/libjsc.so (_ZN3WTF17SharedTaskFunctorIFvvEZN3JSC4Heap13runBeginPhaseENS2_11GCConductorEE4$_17E3runEv+580)
  #09  pc 00000000006171ec  /data/app/{APP_NAME}/lib/arm64/libjsc.so (WTF::ParallelHelperClient::runTask(WTF::RefPtr<WTF::SharedTask<void ()>, WTF::DumbPtrTraits<WTF::DumbPtrTraits>> const&)+40)
  #10  pc 0000000000617950  /data/app/{APP_NAME}/lib/arm64/libjsc.so (WTF::ParallelHelperPool::Thread::work()+16)
  #11  pc 000000000060de7c  /data/app/{APP_NAME}/lib/arm64/libjsc.so (_ZN3WTF8FunctionIFvvEE15CallableWrapperIZNS_15AutomaticThread5startERKNS_14AbstractLockerEE3$_0E4callEv+376)
  #12  pc 000000000061b084  /data/app/{APP_NAME}/lib/arm64/libjsc.so (WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*)+212)
  #13  pc 0000000000646dc8  /data/app/{APP_NAME}/lib/arm64/libjsc.so (WTF::wtfThreadEntryPoint(void*)+4)
  #14  pc 0000000000084148  /system/lib64/libc.so (__pthread_start(void*)+64)
  #15  pc 0000000000023b28  /system/lib64/libc.so (__start_thread+68)

Kudo · 2019-07-25T10:50:44Z

Thank you all and especially @dhess-zynga providing symbolicated backtrace.
It looks like the crash point are mostly the same.
However, I am afraid that I am not able to help with this case if there's no reproduced steps.
The crash seems happened at JSC bytecode being GCed during access.
Without the JS source code & reproduce steps, it is hard to troubleshoot such problem for me.
Maybe it is the time to try upgrading RN 0.60.4 and use Hermes engine.
Or if you need a JSC disabled JIT (based on WebKitGTK 2.24), please feel free to let me know.

mars-lan · 2019-07-25T20:15:00Z

@Kudo Please publish a JIT disabled JSC for us to try out. Unfortunately Hermes isn't an option for some of us yet until intl support is added: facebook/hermes#23

oliverdolgener · 2019-07-30T08:41:06Z

I can confirm crashes on a Huawei Mate 20 Pro running RN 0.59.10:

2019-07-30 10:36:37.063 14725-14944/{APP_NAME} A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20 in tid 14944 (RenderThread), pid 14725 ({APP_NAME})
2019-07-30 10:36:37.146 15316-15316/? I/crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
2019-07-30 10:36:37.147 806-806/? I//system/bin/tombstoned: received crash request for pid 14944
2019-07-30 10:36:37.150 15316-15316/? I/crash_dump64: performing dump of process 14725 (target tid = 14944)
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG: Build fingerprint: 'HUAWEI/LYA-L29/HWLYA:9/HUAWEILYA-L29/146C432R1:user/release-keys'
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG: Revision: '0'
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG: ABI: 'arm64'
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG: pid: 14725, tid: 14944, name: RenderThread  >>> {APP_NAME} <<<
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG: Cause: null pointer dereference
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x0  0000000000000000  x1  0000007cfed3730c  x2  0000000000000002  x3  0000007c585946f8
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x4  0000000000000070  x5  0000007c58593104  x6  0000007c58593100  x7  0000007c585930fc
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x8  0000000000000000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x12 ffffffffffe949dc  x13 0000007c5859c588  x14 0000000000000000  x15 0000000000000000
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x16 0000007cff066118  x17 0000007cfee07d08  x18 0000000000000000  x19 0000000000000000
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x20 0000000000000000  x21 0000007c1717e000  x22 0000000000000000  x23 0000000000000000
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x24 0000000000000000  x25 0000007c5859c588  x26 0000000000000000  x27 0000000000000000
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     x28 0000000000000000  x29 0000007c585946c0
2019-07-30 10:36:37.159 15316-15316/? A/DEBUG:     sp  0000007c585946b0  lr  0000007cfe9be4b8  pc  0000007cfee07d18
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG: backtrace:
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #00 pc 000000000053ed18  /system/lib64/libhwui.so (SkSurface::getCanvas()+16)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #01 pc 00000000000f54b4  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::GLFunctorDrawable::onDraw(SkCanvas*)+1204)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #02 pc 000000000045a8b4  /system/lib64/libhwui.so (SkDrawable::draw(SkCanvas*, SkMatrix const*)+352)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #03 pc 000000000045afc8  /system/lib64/libhwui.so (SkLiteDL::draw(SkCanvas*) const+204)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #04 pc 000000000043e8e0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::drawContent(SkCanvas*) const+292)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #05 pc 000000000043eca0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::forceDraw(SkCanvas*)+252)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #06 pc 000000000045a7e8  /system/lib64/libhwui.so (SkDrawable::draw(SkCanvas*, SkMatrix const*)+148)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #07 pc 000000000045afc8  /system/lib64/libhwui.so (SkLiteDL::draw(SkCanvas*) const+204)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #08 pc 000000000043e8e0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::drawContent(SkCanvas*) const+292)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #09 pc 000000000043eca0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::forceDraw(SkCanvas*)+252)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #10 pc 000000000045a7e8  /system/lib64/libhwui.so (SkDrawable::draw(SkCanvas*, SkMatrix const*)+148)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #11 pc 000000000045afc8  /system/lib64/libhwui.so (SkLiteDL::draw(SkCanvas*) const+204)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #12 pc 000000000043e8e0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::drawContent(SkCanvas*) const+292)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #13 pc 000000000043eca0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::forceDraw(SkCanvas*)+252)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #14 pc 000000000045a7e8  /system/lib64/libhwui.so (SkDrawable::draw(SkCanvas*, SkMatrix const*)+148)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #15 pc 000000000045afc8  /system/lib64/libhwui.so (SkLiteDL::draw(SkCanvas*) const+204)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #16 pc 000000000043e8e0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::drawContent(SkCanvas*) const+292)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #17 pc 000000000043eca0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::forceDraw(SkCanvas*)+252)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #18 pc 000000000045a7e8  /system/lib64/libhwui.so (SkDrawable::draw(SkCanvas*, SkMatrix const*)+148)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #19 pc 000000000045afc8  /system/lib64/libhwui.so (SkLiteDL::draw(SkCanvas*) const+204)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #20 pc 000000000043e8e0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::drawContent(SkCanvas*) const+292)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #21 pc 000000000043eca0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::forceDraw(SkCanvas*)+252)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #22 pc 000000000045a7e8  /system/lib64/libhwui.so (SkDrawable::draw(SkCanvas*, SkMatrix const*)+148)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #23 pc 000000000045afc8  /system/lib64/libhwui.so (SkLiteDL::draw(SkCanvas*) const+204)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #24 pc 000000000043e8e0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::drawContent(SkCanvas*) const+292)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #25 pc 000000000043eca0  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::RenderNodeDrawable::forceDraw(SkCanvas*)+252)
2019-07-30 10:36:37.192 15316-15316/? A/DEBUG:     #26 pc 00000000000fdc3c  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::SkiaPipeline::renderLayersImpl(android::uirenderer::LayerUpdateQueue const&, bool, bool)+784)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #27 pc 000000000047f848  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::SkiaPipeline::renderFrame(android::uirenderer::LayerUpdateQueue const&, SkRect const&, std::__1::vector<android::sp<android::uirenderer::RenderNode>, std::__1::allocator<android::sp<android::uirenderer::RenderNode>>> const&, bool, bool, android::uirenderer::Rect const&, sk_sp<SkSurface>)+96)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #28 pc 000000000047e270  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::SkiaOpenGLPipeline::draw(android::uirenderer::renderthread::Frame const&, SkRect const&, SkRect const&, android::uirenderer::FrameBuilder::LightGeometry const&, android::uirenderer::LayerUpdateQueue*, android::uirenderer::Rect const&, bool, bool, android::uirenderer::BakedOpRenderer::LightInfo const&, std::__1::vector<android::sp<android::uirenderer::RenderNode>, std::__1::allocator<android::sp<android::uirenderer::Re
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #29 pc 0000000000108ffc  /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw()+240)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #30 pc 00000000004838d0  /system/lib64/libhwui.so (_ZNSt3__110__function6__funcIZN7android10uirenderer12renderthread13DrawFrameTask11postAndWaitEvE3$_0NS_9allocatorIS6_EEFvvEEclEv$c303f2d2360db58ed70a2d0ac7ed911b+644)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #31 pc 000000000043d828  /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+168)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #32 pc 00000000001167a8  /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+240)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #33 pc 000000000000fa44  /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #34 pc 0000000000082dfc  /system/lib64/libc.so (__pthread_start(void*)+36)
2019-07-30 10:36:37.193 15316-15316/? A/DEBUG:     #35 pc 0000000000024080  /system/lib64/libc.so (__start_thread+68)

smoczynskicitiz · 2019-07-30T15:53:10Z

Hello !

I just updated my application on the PlayStore today, I use now the RN version 0.59.10, and I have this problem on a device. I saw this on the Google Play Console.

The device is Galaxy S8+ (dream2lte) on Android 9.

backtrace:
  #00  pc 00000000000f7748  /data/data/{package_name}/lib-0/libjsc.so (JSC::AccessCase::propagateTransitions(JSC::SlotVisitor&) const+16)
  #01  pc 0000000000143fe8  /data/data/{package_name}/lib-0/libjsc.so (JSC::PolymorphicAccess::propagateTransitions(JSC::SlotVisitor&) const+48)
  #02  pc 000000000012f0a8  /data/data/{package_name}/lib-0/libjsc.so (JSC::CodeBlock::propagateTransitions(JSC::ConcurrentJSLocker const&, JSC::SlotVisitor&)+556)
  #03  pc 0000000000139484  /data/data/{package_name}/lib-0/libjsc.so (JSC::ExecutableToCodeBlockEdge::runConstraint(JSC::ConcurrentJSLocker const&, JSC::VM&, JSC::SlotVisitor&)+40)
  #04  pc 000000000013900c  /data/data/{package_name}/lib-0/libjsc.so (JSC::ExecutableToCodeBlockEdge::visitChildren(JSC::JSCell*, JSC::SlotVisitor&)+1044)
  #05  pc 00000000001fb9c4  /data/data/{package_name}/lib-0/libjsc.so (_ZZN3JSC11SlotVisitor5drainEN3WTF13MonotonicTimeEENK3$_3clERNS_14MarkStackArrayE+324)
  #06  pc 00000000001f8e90  /data/data/{package_name}/lib-0/libjsc.so (JSC::SlotVisitor::drain(WTF::MonotonicTime)+132)
  #07  pc 00000000001f96bc  /data/data/{package_name}/lib-0/libjsc.so (JSC::SlotVisitor::drainFromShared(JSC::SlotVisitor::SharedDrainMode, WTF::MonotonicTime)+580)
  #08  pc 00000000001e41a0  /data/data/{package_name}/lib-0/libjsc.so (_ZN3WTF17SharedTaskFunctorIFvvEZN3JSC4Heap13runBeginPhaseENS2_11GCConductorEE4$_17E3runEv+580)
  #09  pc 00000000006171ec  /data/data/{package_name}/lib-0/libjsc.so (WTF::ParallelHelperClient::runTask(WTF::RefPtr<WTF::SharedTask<void ()>, WTF::DumbPtrTraits<WTF::DumbPtrTraits>> const&)+40)
  #10  pc 0000000000617950  /data/data/{package_name}/lib-0/libjsc.so (WTF::ParallelHelperPool::Thread::work()+16)
  #11  pc 000000000060de7c  /data/data/{package_name}/lib-0/libjsc.so (_ZN3WTF8FunctionIFvvEE15CallableWrapperIZNS_15AutomaticThread5startERKNS_14AbstractLockerEE3$_0E4callEv+376)
  #12  pc 000000000061b084  /data/data/{package_name}/lib-0/libjsc.so (WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*)+212)
  #13  pc 0000000000646dc8  /data/data/{package_name}/lib-0/libjsc.so (WTF::wtfThreadEntryPoint(void*)+4)
  #14  pc 0000000000084dc0  /system/lib64/libc.so (__pthread_start(void*)+208)
  #15  pc 0000000000023a4c  /system/lib64/libc.so (__start_thread+68)

janczizikow · 2019-07-30T16:11:43Z

I've also saw similar crashes on multiple devices in Google Play Store crash report.
Unfortunately I cannot easily upgrade to 0.60+ and try out Hermes. Anyone tried upgrading and trying out Hermes yet?

RN: 0.59.10
Android 9
Devices:

Pixel 3 (blueline)
Nokia 7 plus (B2N_sprout)
Galaxy S9 (starlte)
Pixel 2 (walleye)
Pixel 3 XL (crosshatch)
Galaxy S10+ (beyond2)

backtrace:

  #00  pc 00000000000f7748  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (JSC::AccessCase::propagateTransitions(JSC::SlotVisitor&) const+16)
  #01  pc 0000000000143fe8  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (JSC::PolymorphicAccess::propagateTransitions(JSC::SlotVisitor&) const+48)
  #02  pc 000000000012f0a8  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (JSC::CodeBlock::propagateTransitions(JSC::ConcurrentJSLocker const&, JSC::SlotVisitor&)+556)
  #03  pc 0000000000139484  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (JSC::ExecutableToCodeBlockEdge::runConstraint(JSC::ConcurrentJSLocker const&, JSC::VM&, JSC::SlotVisitor&)+40)
  #04  pc 000000000013900c  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (JSC::ExecutableToCodeBlockEdge::visitChildren(JSC::JSCell*, JSC::SlotVisitor&)+1044)
  #05  pc 00000000001fb9c4  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (_ZZN3JSC11SlotVisitor5drainEN3WTF13MonotonicTimeEENK3$_3clERNS_14MarkStackArrayE+324)
  #06  pc 00000000001f8e90  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (JSC::SlotVisitor::drain(WTF::MonotonicTime)+132)
  #07  pc 00000000001f96bc  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (JSC::SlotVisitor::drainFromShared(JSC::SlotVisitor::SharedDrainMode, WTF::MonotonicTime)+580)
  #08  pc 00000000001e41a0  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (_ZN3WTF17SharedTaskFunctorIFvvEZN3JSC4Heap13runBeginPhaseENS2_11GCConductorEE4$_17E3runEv+580)
  #09  pc 00000000006171ec  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (WTF::ParallelHelperClient::runTask(WTF::RefPtr<WTF::SharedTask<void ()>, WTF::DumbPtrTraits<WTF::DumbPtrTraits>> const&)+40)
  #10  pc 0000000000617950  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (WTF::ParallelHelperPool::Thread::work()+16)
  #11  pc 000000000060de7c  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (_ZN3WTF8FunctionIFvvEE15CallableWrapperIZNS_15AutomaticThread5startERKNS_14AbstractLockerEE3$_0E4callEv+376)
  #12  pc 000000000061b084  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*)+212)
  #13  pc 0000000000646dc8  /data/app/{package_name}-1_OKn7xVjBSXDhWrN582vQ==/lib/arm64/libjsc.so (WTF::wtfThreadEntryPoint(void*)+4)
  #14  pc 0000000000083530  /system/lib64/libc.so (__pthread_start(void*)+36)
  #15  pc 00000000000241dc  /system/lib64/libc.so (__start_thread+68)

j-wang · 2019-07-30T23:01:21Z

We see it intermittently as well... ~~Unfortunately, Hermes doesn't yet support some things that are relatively common in our codebase (and I think that of a lot of folks), specifically~~ (Actually I just realized it's probably babel'ed in—we'll probably try it on our side and report back):

let and const (block scoped variables, with support for the temporal dead zone)
Classes and method definitions
Computed property keys on object literals
ES modules (import and export)

https://github.com/facebook/hermes/blob/master/doc/Features.md

Despite heroic efforts to track it down/fix it from @Kudo and folks, it might be worth going backward vs. forward to before 0.59, when the JSC was upgraded. We like trying to stay updated on features, but crashes/freezing/etc. on production apps that we can't stop are making us consider waiting until 0.60+/Hermes is more mature to actually have hooks, etc. that came with 0.59+.

oliverdolgener · 2019-07-31T13:42:56Z

Hey guys, I've found what caused the problem in our app. we are using react-navigation in combination with useScreens. There seems to be a problem in the useScreens code:

software-mansion/react-native-screens#105

deactivating and removing useScreens seems to fix the crashes

mars-lan · 2019-07-31T13:48:41Z

Can confirm that I too use react-navigation but not using useScreens.

smoczynskicitiz · 2019-07-31T13:51:27Z

Hey,

Same as @mars-lan , using react-navigation 3.0.0 but not useScreens.

j-wang · 2019-07-31T21:50:55Z

We also use react-navigation (3.7.1) as well—but similar to the other folks here, don't use useScreens. One of our early theories was something with navigation (since it seemed to happen more often when we interacted with navigation elements). We had cleared it later after seeing other reports that seemed to say they didn't have it, but will test on our side and see if it resolves it.

thomasonweb · 2019-08-02T14:32:31Z

We have released React Native 0.60.4 on Wednesday using Hermes on Android and I can confirm there are no more 64-bit crashes (at least not yet at this point). In fact, Hermes improved our average app boot time from 5.8s to 2.5s or even less on higher end devices.

One thing to note: If you support Android 4 you should use the latest version of "hermes-engine" (0.1.1) as the current "hermesvm" (0.1.0) integration in React Native 0.60.4 makes the app crash on boot time. See facebook/hermes#42 for more info on that.

blohamen · 2019-08-07T08:29:00Z

Hi all.
I updated app to RN 0.60.4 but crashes still have. I tested on real devices, but i can't give backtrace :(
Devices with crash:
htc u11 plus 8.0
Huawei nexus 6p 8.1
Motorola moto g6 8.0
LGE Nexus 5X Android 8.0.0
samsung galaxy S8 8 0
samsung galaxy S8 PLUS 8 0
samsung galaxy S9 8 0
samsung galaxy S9 Plus 8 0
sony Xperia xa 1 80
Sony Xperia XZ2 Android 8.0.0
I must say right away that it’s impossible to turn on Hermes because Realm Db cannot work with it yet

Updated:

Well, it is my fail. This is a crash not because of JSC but because of a problem with portrait mode in SDK 26 (android 8)

john1jan · 2019-08-09T07:56:34Z

Same crash hapening for me as well

F/libc (14838): Fatal signal 11 (SIGSEGV) in tid 14959 (mqt_js)
F/libc (14838): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xa6cca6cc510534

loginov-rocks · 2019-08-09T23:03:06Z

Hey guys, this appears to be absolute blocker for all Android apps using React Native to be updated since Google Play not allow to push apps without 64 bit support from Aug 1.

And we can't go back to previous RN versions since they don't support 64 bit at all. Am I missing something? Please correct.

It's not clear if anybody from React Native team aware of that. Is there any way to escalate this issue?

bsonmez · 2020-11-02T05:31:18Z

react-native: 0.61.5 has the same issue as well

Anujmoglix · 2020-11-02T08:46:06Z

every version is having that issue

Boubaker93 · 2020-11-02T09:26:58Z

@RodolfoGS i can confirm that. i'm having that exact same issue me too !
And i started getting that issue when i upgraded from react native 0.62.2 to 0.63.2

evelant · 2020-11-02T17:25:05Z

We had some success in reducing these native crashes by eliminating 3rd party dependencies (Instabug and Smartlook were causing some in our case).

We also had a reduction in crashes by eliminating use of animated value listeners. Turns out that AnimatedValue.addListener is incredibly expensive even if your callback does zero work. If you have more than 5 listeners active at once it can cause all sorts of strange crashes in native and java, break the debugger, cause hangs, and generally wreak havoc with no indication that it's the source of the problem.... IMO after going through a long ordeal to figure out the source of this issue I think that addListener should be marked as experimental or log a warning any time it's used. It's not safe or stable to use.

We also switched to hermes and had lots of crashes and hangs there until we resolved the above issue with animated value listeners. Now the app is much more stable, fast, and lightweight on hermes.

tl;dr -- remove your 3rd party deps and remove animated value listeners first and then try hermes and your issues may disappear

rumax · 2020-11-04T08:04:53Z

Hermes doesn't seems to be a good replacement for JSC, because the app starts to consume 2 times more memory and looking into comments above it even does not guaranty the fix. That issue definitely requires more attention and support.

F170x · 2020-11-04T14:09:20Z

More than 1 year that issue was created, 118 comments, 57 participants... Assignees: No one assigned 🙄

adbs1 · 2020-11-10T18:04:26Z

Apologies if this is white noise but I don't see any mention of animated WebViews here when they seem to be a common theme with this error.

react-native-webview/react-native-webview#429

The following code produces the signal 11 crash every time in our app when the default react-navigation animation is enabled. Two things prevent the crashing, 1) removing the WebView from the first scene (not an option for us), or 2) removing the animation by using the animationEnabled:false option.

<AppStack.Navigator
headerMode="none"
mode="modal"
initialRouteName={'WebView'}
screenOptions={{ gestureEnabled: false, animationEnabled: false }}>
<Stack.Screen name="WebView" component={WebViewScene} />
<Stack.Screen name="SomeOther" component={SomeOtherScene} />
</AppStack.Navigator>

There is a lot of chat in the wild about AdMob bringing apps down when it randomly inserts adverts containing WebViews.

The crashing was happening consistently on the following in our test device:

Android 10 on a Galaxy Note 9
"react-native": "0.63.2"
"@react-navigation/native": "^5.8.8"
"@react-navigation/stack": "^5.12.5"
"react-native-screens": "^2.13.0"

RodolfoGS · 2020-11-10T19:05:13Z

There is a lot of chat in the wild about AdMob bringing apps down when it randomly inserts adverts containing WebViews.

@adbs1 Can you explain more about this?

adbs1 · 2020-11-12T09:09:24Z

@RodolfoGS Very late here so I'll leave you these:

invertase/react-native-firebase#2935 (comment)
react-native-webview/react-native-webview#575 (comment)

bb2002 · 2021-01-24T05:16:52Z

Same issue in RN 0.63.4, React 16.13.1
In my case, i can solved problem by appling style={{ opacity: 0.99 }} in my <WebView />

zuhairnaqi · 2021-01-25T14:07:26Z

If having issue with react-native-webview check this comment webview#575

RodolfoGS · 2021-02-11T16:05:45Z

Hi @zuhairnaqi, I'm having that issue but I'm using admob, and I think that sometimes they show ads on a webview, but I haven't options to disable hardware acceleration in the admob library, I'm using @react-native-firebase/admob

Do you know how can I disable hardware acceleration there?

Thanks,

zuhairnaqi · 2021-02-11T18:31:02Z

@RodolfoGS Sorry don't know and never used this library

trizin · 2021-02-20T18:16:39Z

Switching to v8 fixed the problem for me! No crashes so far.

ttkien · 2021-03-09T03:49:26Z

Switching to v8 fixed the problem for me! No crashes so far.

@trizin Could you help me How to switch to v8?

trizin · 2021-03-09T07:31:46Z

@ttkien Sure, it's pretty simple. You need to install the package and modify your build.gradle. Follow the steps here. I suggest you use the v8-android-nointl this will reduce your app size. The only difference is it doesn't contain intl. As far as I know "react native" doesn't have it too so it shouldn't be a problem.

Summary: Upgrade jsc-android to latest stable version. Hopefully this should finally fix facebook#25494. Before Hermes totally replaced JSC, it should be worth to have this and make JSC stable ## Changelog [Android] [Changed] - Upgrade jsc-android to 250230.2.1 Pull Request resolved: facebook#31304 Test Plan: Launch app with new jsc-android and see everything works fine. Reviewed By: TheSavior Differential Revision: D28630503 Pulled By: yungsters fbshipit-source-id: 84510f91c81d4aaefe265d5492677ad6ff10e0fe

Summary: Upgrade jsc-android to latest stable version. Hopefully this should finally fix #25494. Before Hermes totally replaced JSC, it should be worth to have this and make JSC stable ## Changelog [Android] [Changed] - Upgrade jsc-android to 250230.2.1 Pull Request resolved: #31304 Test Plan: Launch app with new jsc-android and see everything works fine. Reviewed By: TheSavior Differential Revision: D28630503 Pulled By: yungsters fbshipit-source-id: 84510f91c81d4aaefe265d5492677ad6ff10e0fe

shivam0831 · 2021-08-17T12:16:08Z

I am still getting this error, any solution?

Samsung Galaxy S8+
Android 9 (SDK 28)

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
libjsc.so

pid: 0, tid: 0 >>> com.myapp<<<

backtrace:
#00 pc 00000000000f7748 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 0000000000143fe8 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 000000000012f0a8 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 0000000000139484 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 000000000013900c /data/data/com.myapp/lib-0/libjsc.so
#00 pc 00000000001fb9c4 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 00000000001f8e90 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 00000000001f96bc /data/data/com.myapp/lib-0/libjsc.so
#00 pc 00000000001e41a0 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 00000000006171ec /data/data/com.myapp/lib-0/libjsc.so
#00 pc 0000000000617950 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 000000000060de7c /data/data/com.myapp/lib-0/libjsc.so
#00 pc 000000000061b084 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 0000000000646dc8 /data/data/com.myapp/lib-0/libjsc.so
#00 pc 0000000000084e00 /system/lib64/libc.so (__pthread_start(void*)+208)
#00 pc 0000000000023a8c /system/lib64/libc.so (__start_thread+68)

txvnt · 2021-11-01T20:45:03Z

for me it was that I was using the wrong version of Hermes for my project. You can look up the correct version for you here https://github.com/facebook/hermes/releases

Hope it helps!

zhy1023 · 2022-07-06T02:02:07Z

How to solve the following problems?

    vivo v2061a

Android 10 (SDK 30)

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000000000010
libjsc.so

pid: 0, tid: 0 >>> com.myapp<<<

#00 pc 00000000000f7748 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZNK3JSC10AccessCase20propagateTransitionsERNS_11SlotVisitorE+16)
#1 pc 0000000000143fe8 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZNK3JSC17PolymorphicAccess20propagateTransitionsERNS_11SlotVisitorE+48)
#2 pc 000000000012f0a8 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3JSC9CodeBlock20propagateTransitionsERKNS_18ConcurrentJSLockerERNS_11SlotVisitorE+556)
#3 pc 0000000000139484 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3JSC25ExecutableToCodeBlockEdge13runConstraintERKNS_18ConcurrentJSLockerERNS_2VMERNS_11SlotVisitorE+40)
#4 pc 000000000013900c /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3JSC25ExecutableToCodeBlockEdge13visitChildrenEPNS_6JSCellERNS_11SlotVisitorE+1044)
#5 pc 00000000001fb9c4 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZZN3JSC11SlotVisitor5drainEN3WTF13MonotonicTimeEENK3$_3clERNS_14MarkStackArrayE+324)
#6 pc 00000000001f8e90 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3JSC11SlotVisitor5drainEN3WTF13MonotonicTimeE+132)
#7 pc 00000000001f96bc /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3JSC11SlotVisitor15drainFromSharedENS0_15SharedDrainModeEN3WTF13MonotonicTimeE+580)
#8 pc 00000000001e41a0 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3WTF17SharedTaskFunctorIFvvEZN3JSC4Heap13runBeginPhaseENS2_11GCConductorEE4$_17E3runEv+580)
#9 pc 00000000006171ec /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3WTF20ParallelHelperClient7runTaskERKNS_6RefPtrINS_10SharedTaskIFvvEEENS_13DumbPtrTraitsIS4_EEEE+40)
#10 pc 0000000000617950 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3WTF18ParallelHelperPool6Thread4workEv+16)
#11 pc 000000000060de7c /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3WTF8FunctionIFvvEE15CallableWrapperIZNS_15AutomaticThread5startERKNS_14AbstractLockerEE3$_0E4callEv+376)
#12 pc 000000000061b084 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE+212)
#13 pc 0000000000646dc8 /data/app/com.xxx.xxx-RyQEpiqg2bYRiq2ThRjaag==/lib/arm64/libjsc.so (_ZN3WTFL19wtfThreadEntryPointEPv+4)
#14 pc 000000000008f778 /apex/com.android.runtime/lib64/bionic/libc.so (_ZL15__pthread_startPv+36)
#15 pc 0000000000031dc4 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)

ebaynaud added the Bug label Jul 4, 2019

ebaynaud mentioned this issue Jul 4, 2019

App Crash on Android OS 6 Samsung Galaxy S7 SM-G930FD (JSC Crash) 64 bit support A/libc: Fatal signal 11 (SIGSEGV) #24261

Closed

ebaynaud changed the title ~~signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41~~ signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41 (Android 8.0) Jul 4, 2019

react-native-bot added the Platform: Android Android applications. label Jul 4, 2019

flexsurfer mentioned this issue Jul 30, 2019

Fix 64bit apk freezes on arm64 hardware status-im/status-mobile#8665

Closed

j-wang mentioned this issue Jul 30, 2019

react-native 0.59.10 in Back off at Android 4.1.2 #25806

Closed

Invertisment mentioned this issue Mar 14, 2021

WebView rerender crashes on Android API 28+ react-native-webview/react-native-webview#1915

Closed

adbs1 mentioned this issue Mar 30, 2021

[ANDROID] Crashes appeared around March 13th (Chrome 73) react-native-webview/react-native-webview#429

Closed

DerekNien mentioned this issue Mar 31, 2021

when you use navigation.navigate the app crash on android using webview because androidHardwareAccelerationDisabled iou90/react-native-autoheight-webview#191

Closed

Kudo mentioned this issue Apr 6, 2021

Upgrade jsc-android to 250230.2.1 #31304

Closed

facebook-github-bot closed this as completed in 341f061 May 24, 2021

narin mentioned this issue Apr 22, 2022

BUG - Sev-2 - Android - libc.so crash department-of-veterans-affairs/va-mobile-app#3013

Closed

2 tasks

FlorenceChashchina mentioned this issue Jul 18, 2022

SIGSEGV in MainActivity msupply-foundation/mobile#4803

Closed

andreialecu mentioned this issue Mar 8, 2023

fix(android): Prevent libhwui crash when WebView is in ScrollView react-native-webview/react-native-webview#2874

Merged

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41 (Android 8.0) #25494

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41 (Android 8.0) #25494

Comments

ebaynaud commented Jul 4, 2019 • edited Loading

Kudo commented Jul 4, 2019

ebaynaud commented Jul 4, 2019

thomasonweb commented Jul 9, 2019

xanderdeseyn commented Jul 15, 2019

jsaraiva commented Jul 20, 2019 • edited Loading

mars-lan commented Jul 20, 2019

xanderdeseyn commented Jul 23, 2019

j-wang commented Jul 23, 2019

dhess-zynga commented Jul 24, 2019

mcuelenaere commented Jul 25, 2019 • edited Loading

Kudo commented Jul 25, 2019

mars-lan commented Jul 25, 2019

oliverdolgener commented Jul 30, 2019

smoczynskicitiz commented Jul 30, 2019

janczizikow commented Jul 30, 2019

j-wang commented Jul 30, 2019 • edited Loading

oliverdolgener commented Jul 31, 2019 • edited Loading

mars-lan commented Jul 31, 2019

smoczynskicitiz commented Jul 31, 2019

j-wang commented Jul 31, 2019 • edited Loading

thomasonweb commented Aug 2, 2019

blohamen commented Aug 7, 2019 • edited Loading

Updated:

john1jan commented Aug 9, 2019

loginov-rocks commented Aug 9, 2019

bsonmez commented Nov 2, 2020

Anujmoglix commented Nov 2, 2020

Boubaker93 commented Nov 2, 2020 • edited Loading

evelant commented Nov 2, 2020 • edited Loading

rumax commented Nov 4, 2020 • edited Loading

F170x commented Nov 4, 2020

adbs1 commented Nov 10, 2020

RodolfoGS commented Nov 10, 2020 • edited Loading

adbs1 commented Nov 12, 2020

bb2002 commented Jan 24, 2021 • edited Loading

zuhairnaqi commented Jan 25, 2021

RodolfoGS commented Feb 11, 2021

zuhairnaqi commented Feb 11, 2021

trizin commented Feb 20, 2021

ttkien commented Mar 9, 2021

trizin commented Mar 9, 2021

shivam0831 commented Aug 17, 2021 • edited Loading

txvnt commented Nov 1, 2021

zhy1023 commented Jul 6, 2022

ebaynaud commented Jul 4, 2019 •

edited

Loading

jsaraiva commented Jul 20, 2019 •

edited

Loading

mcuelenaere commented Jul 25, 2019 •

edited

Loading

j-wang commented Jul 30, 2019 •

edited

Loading

oliverdolgener commented Jul 31, 2019 •

edited

Loading

j-wang commented Jul 31, 2019 •

edited

Loading

blohamen commented Aug 7, 2019 •

edited

Loading

Boubaker93 commented Nov 2, 2020 •

edited

Loading

evelant commented Nov 2, 2020 •

edited

Loading

rumax commented Nov 4, 2020 •

edited

Loading

RodolfoGS commented Nov 10, 2020 •

edited

Loading

bb2002 commented Jan 24, 2021 •

edited

Loading

shivam0831 commented Aug 17, 2021 •

edited

Loading