libc.so Crash report by firebase crashlytics in android app

[RajeshRRathod]

Description

libc.so
Crashed: Thread #1
SIGSEGV 0x0000000000000020

We can not reproduce crash in some device so this issue device specific or not ?
Please Give me solution for this crash asap.

open this link to check device list to crash
Crash device list by firebase crashlytics

> HUAWEI (86% )

• Honor 10

> Samsung (6%)

• Galaxy Note9
• Galaxy S9
• Galaxy A13 5G
• Galaxy A02s

> Xiaomi (3%)

• Redmi 6
• POCO M3

> Realme (2%)

• realme C11

> INFINIX MOBILITY LIMITED (1%)

Version

0.63.4

Output of npx react-native info

System:
OS: macOS 12.1
CPU: (4) x64 Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz
Memory: 36.70 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 15.14.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 7.7.6 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 23, 28, 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.3
System Images: android-29 | Android TV Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.7199119
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_282 - /usr/bin/javac
Python: 2.7.18 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.63.4 => 0.63.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Steps to reproduce

We can check multiple devices , but we can not reproduce this crash
we can not reproduce this Crash from below device list

• Redmi note 7s (OS : 10),
• Samsung Galaxy F62 (OS : 11),
• Huwai (OS : 8.1),
• OnePlus 3 (OS : 11),
• OnePlus node (OS : 11),
• Samsung m31s (OS:11),
• realme (OS:11),

Snack, code example, screenshot, or link to a repository

0 libhwui.so (Missing UUID dea0f9eed9d9ace602a4e6115205e264)
1 libhwui.so (Missing UUID dea0f9eed9d9ace602a4e6115205e264)
2 libhwui.so (Missing UUID dea0f9eed9d9ace602a4e6115205e264)
3 libhwui.so (Missing UUID dea0f9eed9d9ace602a4e6115205e264)

No response

[bigyank]

I can confirm that I too got the same crash report.
Further investigating, I found that this could be a recurring issue on Samsung devices [1][2][3].

Here's a similar thread on this issue.

Furthermore, in my case, this issue was seen on A12 Samsung devices when the app was launched with wifi on, and then it crashed when the wifi was turned off. I found a thread on this exact issue here

[bigyank]

Has there been any update on this?

[IseeUDenis]

I also met this issues. Is there any solution for this?

[Filippo39]

I also have the same issue, 200 crashes and 75% due to Samsung devices such as:

• Galaxy A51
• Galaxy S10+
• Galaxy S10e
• Galaxy S10
• Galaxy S21 FE 5G
• Galaxy Note10+
• Galaxy S20+
• Galaxy Note10 Lite
• Galaxy S20 Ultra 5G
• Galaxy Z Flip3 5G
• Galaxy A13
• ...

[deggertsen]

Similar issues on RN 0.67.3
228 crash events affecting 219 users in the last 24 hours. 86% Samsung.

Crashed: Thread :  SIGSEGV  0x0000000000000048
#00 pc 0x6703bc libjsc.so 
#01 pc 0x624 linux-vdso.so.1 
#02 pc 0x16524 libutils.so 
#03 pc 0x16408 libutils.so 
#04 pc 0x151dcc libandroid_runtime.so 

[haisamMH]

I am also having the issue. Any update, please?

[HessiPard]

same issue :/ any update?

[3NM79]

We're also facing the same issue with Samsung immediately after the first screen in the app gets mounted
Device: Galaxy A52 5G

[haisamMH]

I have got rid of this issue by enabling Hermes

[3NM79]

Hey Hysham! Were you facing lots of crashes prior to enabling Hermes or just a few? I'm just trying to understand if that would really solve the root cause of the issue

[haisamMH]

It was a silent native crash on initial rendering after installation, I found the error on logcat as follows "libc.so SIGSEGV 0x0000000000000048 crash"

I understood it might be something messed with jsc engine.

I hope this post would be helpful : https://stackoverflow.com/questions/65418985/react-native-crashedthread-sigsegv-libjsc-so

[HessiPard]

hi, we faced similar crashes on firebase and google play console too: (only on android 11)

backtrace:
  #00  pc 000000000004e40c  /apex/com.android.runtime/lib64/bionic/libc.so (abort+164)
  #00  pc 0000000000062730  /apex/com.android.runtime/lib64/bionic/libc.so (__stack_chk_fail+20)
  #00  pc 0000000000653b88  /system/lib64/libhwui.so (GrTextStrike::addGlyphToAtlas(SkGlyph const&, GrMaskFormat, bool, GrResourceProvider*, GrDeferredUploadTarget*, GrAtlasManager*, GrGlyph*)+840)
  #00  pc 0000000000657894  /system/lib64/libhwui.so (GrTextBlob::VertexRegenerator::regenerate(int, int)+712)
  #00  pc 000000000061726c  /system/lib64/libhwui.so (GrAtlasTextOp::onPrepareDraws(GrMeshDrawOp::Target*)+1288)
  #00  pc 0000000000513418  /system/lib64/libhwui.so (GrOpsTask::onPrepare(GrOpFlushState*)+356)
  #00  pc 0000000000501c00  /system/lib64/libhwui.so (GrDrawingManager::flush(GrSurfaceProxy**, int, SkSurface::BackendSurfaceAccess, GrFlushInfo const&, GrPrepareForExternalIORequests const&)+1584)
  #00  pc 0000000000502a20  /system/lib64/libhwui.so (GrDrawingManager::flushSurfaces(GrSurfaceProxy**, int, SkSurface::BackendSurfaceAccess, GrFlushInfo const&)+132)
  #00  pc 0000000000532bec  /system/lib64/libhwui.so (GrRenderTargetContext::flush(SkSurface::BackendSurfaceAccess, GrFlushInfo const&)+96)
  #00  pc 000000000056780c  /system/lib64/libhwui.so (SkGpuDevice::flush()+48)
  #00  pc 0000000000218154  /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, android::uirenderer::Rect const&, sk_sp<SkSurface>, SkMatrix const&)+256)
  #00  pc 00000000002151b8  /system/lib64/libhwui.so (android::uirenderer::skiapipeline::SkiaOpenGLPipeline::draw(android::uirenderer::renderthread::Frame const&, SkRect const&, SkRect const&, android::uirenderer::LightGeometry const&, android::uirenderer::LayerUpdateQueue*, android::uirenderer::Rect const&, bool, android::uirenderer::LightInfo const&, std::__1::vector<android::sp<android::uirenderer::RenderNode>, std::__1::allocator<android::sp<android::uirenderer::RenderNode> > > const&, android::uirenderer::FrameInfoVisualizer*)+416)
  #00  pc 000000000021e198  /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw()+832)
  #00  pc 00000000002205ec  /system/lib64/libhwui.so (_ZNSt3__110__function6__funcIZN7android10uirenderer12renderthread13DrawFrameTask11postAndWaitEvE3$_0NS_9allocatorIS6_EEFvvEEclEv$c303f2d2360db58ed70a2d0ac7ed911b+480)
  #00  pc 000000000020ed94  /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+220)
  #00  pc 000000000023006c  /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+88)
  #00  pc 00000000000154cc  /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+260)
  #00  pc 0000000000014d90  /system/lib64/libutils.so (thread_data_t::trampoline(thread_data_t const*)+412)
  #00  pc 00000000000b0048  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+64)
  #00  pc 00000000000503c8  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)

[WBoda]

We're also facing the same issue
any update on this?

[cortinico]

Just a small heads up: without a reproducer this can't be fixed.
Moreover, some of the posted stacktraces have references only of libc and libhwui, which are outside of our control, so I'm unsure this is even related to React Native in the first place.

[github-actions]

⚠️	Missing Reproducible Example
ℹ️	It looks like your issue is missing a reproducible example. Please provide a Snack or a repository that demonstrates the issue you are reporting in a minimal, complete, and reproducible manner.

[bigyank]

I was able to solve the issue was by upgrading React Native version to 0.65.2. My old react native version on which this issue was seen was 0.62.2

[mluksha]

I have the save issue (react-native: 0.67.1) only on Android 12:
Galaxy S20 FE 5G
Galaxy S21 5G
Galaxy S21 Ultra 5G
...

[tarouboy]

Same issue for me, RN 0.66
Devices are more diverse, data coming from around 70 devices:

[sarons]

Had same problem. Hermes was always enabled so that wasn't the issue. It was the WebView, found some solutions here
react-native-webview/react-native-webview#1915

opacity=0.99 in WebView and overScrollMode ="never" in ScrollView fixed the issue. Not a single crash since

[mayankyadav-zepto]

Had same problem. Hermes was always enabled so that wasn't the issue. It was the WebView, found some solutions here react-native-webview/react-native-webview#1915

opacity=0.99 in WebView and overScrollMode ="never" in ScrollView fixed the issue. Not a single crash since

In your case, app was getting crashed when webview was opened? Do you think this might help when the app is crashing on the launch of first activity?

[tamarabernad]

In our case we were having this same crash on Android with error log: libc: Fatal signal 11 (SIGSEGV) ...
We don't have hermes enabled.

We found out that this was due to a compatibility issues of two dependencies: react-native-reanimated v2 + realm as stated in this thread:
realm/realm-js#3837
Realm doesn't have yet support for hermes, they are currently working on it.

We have decided to remove realm from the project and we are not experiencing this crash anymore.

[ponikar]

Is there any way to reproduce this issue in development mode? This issue only exists in production mode.

[github-actions]

This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days.

[Fb9027]

Ok

[wjaykim]

Add compileOptions with JavaVersion 1.8 like this under your app level build.gradle android block:

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

This fixed my issue in RN 0.71

[github-actions]

This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days.

[github-actions]

This issue was closed because the author hasn't provided the requested feedback after 7 days.

[murilogok]

Fixed in RN 0.66.5 by enabling hermes. 0 new occurrences reported.

[roneyyb]

We are still facing this issue majorly on xiaomi and Samsung device after upgrading from react native 0.67.4 to 0.69.9 with hermes enabled. This is the stack trace. Can anyone please provide solution for this?

app_issue_f4e23ef0af3b92e13a709b01f249ecfd_crash_session_646f2d85010f00010a1509de538becb6_DNE_0_v2_stacktrace.txt

[serjek]

I have switched to v8 on android and my user-perceived crash rate went from 8% to below 1% eliminatiing libc.so crash entirely. No performance drawbacks or any other issues discovered for more than 6 months of usage.

[zjkuang]

I have got rid of this issue by enabling Hermes

We still have this issue with hermesEnabled=true

[zjkuang]

Add compileOptions with JavaVersion 1.8 like this under your app level build.gradle android block:

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

This fixed my issue in RN 0.71

We still have this issue with this attempt.

[cnx-caiobarroso]

This shouldn't be closed!
Also experiencing this issue with react-native "0.72.3" with hermes enabled. It isn't viable using v8 or any other because almost every lib uses hermes...

[Arslan106]

Also experiencing this issue with react-native "0.72.6"

[100sarthak100]

Same issue with react-native "0.73.4"

[trungledangAxonActive]

I also got the issue with react native 0.68.7 and hermes is enabled

[rahulpunchh]

having same issue

[AntonioLoco]

having same issue in react-native@0.74.3 and expo@51.0.18 with hermes enabled

[zguo123]

I do not know why this issue is closed. This is clearly an issue.

[2ducanhpham]

This error is too serious and there is still no solution?
With this error we have been warned by Google and listed as a poor quality application.

[serjek]

Guys, give a shot to v8. I've been using it ever since I posted the comment above and quite happy with current crash rate being under 1%. Besides the more users will switch the more prominent it will become for RN maintainers.

[2ducanhpham]

@serjek I am using version 0.70 but v8 integration crashes after opening the app.
I am trying to upgrade to 0.73
After upgrade if error still appear i will try v8 integration

[serjek]

@serjek I am using version 0.70 but v8 integration crashes after opening the app. I am trying to upgrade to 0.73 After upgrade if error still appear i will try v8 integration

did you follow installation steps corretly though? Specifically this one:

[2ducanhpham]

@serjek sure, because integration is simple

[serjek]

Well in that case you shouldn't be observing libjsc.so related crashes, because V8 aims to replace this lib entirely. If that is still the case then perhaps JSC is still somehow crawling into your package - something worth investigation.

[MSinghBhangu]

@serjek @2ducanhpham @tamarabernad @rahulpunchh @cnx-caiobarroso @100sarthak100 Hi , Did you find anything related to this issue causing Sigbart Crash in abundance on start of the application and which is not reproducible happens in release ?

[2ducanhpham]

I have not found the cause and solution yet.