Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Android-RN 0.59.8] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xee0f0434 in tid 16493 (mqt_js)

See original GitHub issue

Hi I want to build my project on RN 0.59.8. MY app use react-native-webgl Building process is fine, but app crashes right after it starts.

A: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xee0f0434 in tid 16493 (mqt_js), pid 16138 (com.testthree)

However, everything works fine on RN 0.57.8

React Native version:

System:
      OS: macOS 10.14.4
      CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
      Memory: 408.59 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
Binaries:
      Node: 12.1.0 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 23, 24, 25, 26, 27, 28
        Build Tools: 23.0.1, 25.0.0, 26.0.1, 27.0.3, 28.0.2, 28.0.3
        System Images: android-28 | Google APIs Intel x86 Atom
IDEs:
      Android Studio: 3.1 AI-173.4720617
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.8 => 0.59.8
    npmGlobalPackages:
      create-react-native-app: 2.0.2
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7
      react-native-rename: 2.2.1

Steps To Reproduce

Init new RN prj with RN 0.59.8
Add react-native-web-gl module
Download NDK 18
Build and run project with react-native run-android

Describe what you expected to happen:

Snack, code example, or link to a repository:

Issue Analytics

State:
Created 4 years ago
Comments:8

Top GitHub Comments

12reactions

RomanovYuriicommented, Jun 2, 2019

Magical part of code saved my life. add this to app/build.gradle: ndk { abiFilters "armeabi-v7a", "x86" }

9reactions

dishantwaliacommented, Jun 2, 2019

@RomanovYurii When we removed 64 bit ndk filters “arm64-v8a”, “x86_64” from ndk abiFilters in defaultConfig block of build.gradle by provide only 32 bit support. The crash has gone but as per Google 64 bit support mandate this needs to be fixed with 64 bit ndk support .

Top Results From Across the Web

Android Fatal signal 11 (SIGSEGV) at 0x636f7d89 (code=1 ...

Your application is accessing memory outside of its address space. This is most likely an invalid pointer access. SIGSEGV = segmentation fault in...

Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault ...

This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. No native Android...

[Android]Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4

Generally crashing only on Samsung S9 and S9+ with some devices and on Firebase Test lab. Production build crashing in Thread 0 (crashed)....

Xamarin Android - Run time crash - [libc] Fatal signal 11 ...

Libc means the error occurs due to native .so file invoking. Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR) means that there is an...

App crashes due to Layout Inspector [201813204]

google.com created issue #1 ... Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x40 in tid 19102 (FinalizerDaemon), pid 19086 (dyandroidclient) ...