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.

SIGSEGV crash in libhwui.so on Pixel android 12 only

See original GitHub issue

Description

I am getting crashes on android. The crash occur only on Pixel devices in production and only on android 12. I am using hermes and react-navigation.

OS Version: Android 12 (SP1A.210812.016.A1)
Report Version: 104

Exception Type: Unknown (SIGSEGV)

Application Specific Information:
Segfault

Thread 0 Crashed:
0   libhwui.so                      0x75d46f04c8        <unknown> + 506075219144
1   libhwui.so                      0x75d48edf58        <unknown> + 506077306712
2   libhwui.so                      0x75d48bea34        <unknown> + 506077112884
3   libhwui.so                      0x75d4aab864        <unknown> + 506079131748
4   libhwui.so                      0x75d48cb8ec        <unknown> + 506077165804
5   libhwui.so                      0x75d46ec850        <unknown> + 506075203664
6   libhwui.so                      0x75d46ec06c        <unknown> + 506075201644
7   libhwui.so                      0x75d468313c        <unknown> + 506074771772
8   libhwui.so                      0x75d46ec8a4        <unknown> + 506075203748
9   libhwui.so                      0x75d46ec06c        <unknown> + 506075201644
10  libhwui.so                      0x75d468313c        <unknown> + 506074771772
11  libhwui.so                      0x75d46ec87c        <unknown> + 506075203708
12  libhwui.so                      0x75d46ec06c        <unknown> + 506075201644
13  libhwui.so                      0x75d468313c        <unknown> + 506074771772
14  libhwui.so                      0x75d46ec8a4        <unknown> + 506075203748
15  libhwui.so                      0x75d46ec06c        <unknown> + 506075201644
16  libhwui.so                      0x75d468313c        <unknown> + 506074771772
17  libhwui.so                      0x75d46ec8a4        <unknown> + 506075203748
18  libhwui.so                      0x75d46ec06c        <unknown> + 506075201644
19  libhwui.so                      0x75d468313c        <unknown> + 506074771772
20  libhwui.so                      0x75d46ec8a4        <unknown> + 506075203748
21  libhwui.so                      0x75d470c338        <unknown> + 506075333432
22  libhwui.so                      0x75d47516d8        <unknown> + 506075616984
23  libhwui.so                      0x75d474ecc0        <unknown> + 506075606208
24  libhwui.so                      0x75d474e828        <unknown> + 506075605032
25  libhwui.so                      0x75d47bcfe0        <unknown> + 506076057568
26  libhwui.so                      0x75d47bbc50        <unknown> + 506076052560
27  libhwui.so                      0x75d47c89f4        <unknown> + 506076105204
28  libhwui.so                      0x75d47c8760        <unknown> + 506076104544
29  libutils.so                     0x75dd7de0b0        android::Thread::_threadLoop
30  libutils.so                     0x75dd7dd968        <unknown> + 506227186024
31  libc.so                         0x75d04db910        __pthread_start
32  libc.so                         0x75d047b3f0        __start_thread
33  <unknown>                       0x0                 <unknown>

Version

0.64.2

Output of `react-native info`

npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.2 => 0.64.2
    react-native-macos: Not Found

Steps to reproduce

It’s hard to reproduce. It occur irregularly in prod only. I couldn’t reproduce it on my pixel 3a.

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

https://play.google.com/store/apps/details?id=com.dietdoctor.EatApp - app

Issue Analytics

State:
Created 2 years ago
Reactions:7
Comments:9 (2 by maintainers)

Top GitHub Comments

10reactions

JensDeTaey27commented, Nov 5, 2021

If you have Webviews in your app you could try and add androidLayerType={'hardware'} to it. I had similar issue and that solved it for me.

1reaction

JungHsuancommented, Dec 16, 2021

In my case, the crash happens only when I navigate to a stack and the initial screen of the stack renders a WebView. I solved this by simply hiding WebView until the transition animation of react-navigation ends. I tried to set animationEnabled=false but It still has animation while opening the stack.

env: react-native: 0.65.1 react-navigation: 6.x react-native-webview: 11.15.0

Top Results From Across the Web

Diagnosing Native Crashes | Android Open Source Project

The following sections include common types of native crash, an analysis of a sample crash dump, and a discussion of tombstones.

android native crash by lib64/libhwui.so , and how to locate ...

maybe it caused by drawing in thread . i add synchronized and fix it. code as follow: synchronized(mCanvas) { mCanvas.

I have no idea how to read this crash report, can anyone help?

Every report is from android version "Unknown", so I'm assuming android L. I can replicate the crash on my own phone running L,...

Real-time crashes, in abort, only in Android 8.1 [70259031]

#02 pc 000000000006c300 /system/lib64/libhwui.so (android::uirenderer:: ... I can see the same crash on my Google Console occurring for Pixel 2 XL and Nokia ......

1074218 - signal 11 (SIGSEGV) in Chrome_InProcGp - Monorail

This template is for filing bugs against Android System WebView. Chrome ... we found that the crashes is coming from libmonochrome.so.