Android Crash: SIGSEGV 0x0000000000000000 - libc.so | Crashed: null pointer dereference #4075

vinayak-bm-ai · 2024-09-09T14:58:45Z

🛑 Blocked by getsentry/sentry-java#3653

Description

Crashed: null pointer dereference #1
SIGSEGV 0x0000000000000000

libc.so
(Missing BuildId d1a98b526f2f94260a53c3055979a4f6)

We've observed that this crash spiked on 7th Sep. We've seen that [sentry-java](https://github.com/getsentry/sentry-java/releases/tag/7.0.0-rc.2 here) provided the fix for these issues. but we're still seeing this error with the sentry SDK versions mentioned below.

React Native Version: 0.71.13 with Hermes enabled

 "@sentry/react": "^7.75.0",
 "@sentry/react-native": "^5.22.3",
 "@sentry/tracing": "^7.75.0",
 "@sentry/types": "^7.75.0",
 "@sentry/utils": "^7.75.0",

After investigating the statistics in Firebase Crashlytics, I found

It is happening mostly on Android 12+ devices.
Could not relate this to the memory shortage, devices had free memory (Adding screenshots for the same).

Steps to reproduce

Not able to reproduce this issue as this has been occurring randomly on Android devices.

React Native Version

0.71.13

Affected Platforms

Runtime - Android

Output of `npx react-native info`

System:
    OS: macOS 14.6.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 37.20 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    Yarn: Not Found
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
    Watchman: 2024.08.26.00 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.13.0 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
    Android SDK:
      API Levels: 23, 28, 29, 30, 31, 33, 33, 34
      Build Tools: 30.0.2, 30.0.3, 33.0.0, 33.0.2, 34.0.0
      System Images: android-30 | Google APIs Intel x86 Atom, android-31 | Google APIs Intel x86_64 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 2022.3 AI-223.8836.35.2231.10811636
    Xcode: 15.2/15C500b - /usr/bin/xcodebuild
  Languages:
    Java: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0 
    react-native: 0.71.13 => 0.71.13 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Stacktrace or Logs

null pointer dereference: SIGSEGV  0x0000000000000000
#00 pc 0x96850 libc.so (BuildId: d1a98b526f2f94260a53c3055979a4f6)
#01 pc 0x5b510c libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#02 pc 0x5b487c libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#03 pc 0x5b6814 libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#04 pc 0x54eeb0 libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#05 pc 0x5b6148 libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#06 pc 0x933e24 libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#07 pc 0x93023c libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#08 pc 0x160fc libbase.so (BuildId: 42d41ca7c77853791d096606e7186547)
#09 pc 0x156d0 libbase.so (BuildId: 42d41ca7c77853791d096606e7186547)
#10 pc 0x5b74ec libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#11 pc 0x30b2b4 libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#12 pc 0x63eec8 libart.so (BuildId: 7300f6c36a74cc43266451736b120528)
#13 pc 0x104fc4 libc.so (BuildId: d1a98b526f2f94260a53c3055979a4f6)
#14 pc 0x9e764 libc.so (BuildId: d1a98b526f2f94260a53c3055979a4f6)

Reproducer

NA

Screenshots and Videos

com.brightcapital.app_issue_f4e23ef0af3b92e13a709b01f249ecfd_crash_session_66dea84e0283000168d5d19a075ad28a_DNE_0_v2_stacktrace (1).txt

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

krystofwoldrich · 2024-09-10T08:19:27Z

Hi @vinayak-bm-ai,

thank you for the message.

Did the spike happen without any changes on your side, no new version...?

Linking the possibly related issue from sentry-java

The number of Crashes and ANRs has increased sentry-java#2955

krystofwoldrich · 2024-09-10T08:20:13Z

@markushi I don't have context of the original Android issue, could you take a look?

vinayak-bm-ai · 2024-09-10T08:40:40Z

Yes @krystofwoldrich , we haven’t made any changes to the codebase, no new version

markushi · 2024-09-10T09:33:14Z

@vinayak-bm-ai thanks for sharing all the details! I took a look at the attached stacktrace, and there's no sentry symbol involved in the crashing thread. Why do you think this is caused by sentry?

On top of that could you share your sentry config options with us?

vinayak-bm-ai · 2024-09-10T10:45:28Z

Hey @markushi We're unable to reproduce this crash as it suddenly spiked out of nowhere. After researching, we found that sentry-java had a similar issue before, and since sentry-android uses it, the fix for this issue has been added to sentry-react-native. (https://github.com/getsentry/sentry-java/releases/tag/7.0.0-rc.2 here) can you also check this once?
Also, the crash count is increasing day by day.

vinayak-bm-ai · 2024-09-10T11:39:14Z

Sentry.init({
      dsn: dns,
      environment: env,
      debug: false,
      integrations: [
        new Sentry.ReactNativeTracing({
          enableUserInteractionTracing: true,
          routingInstrumentation,
        }),
        Sentry.metrics.metricsAggregatorIntegration(),
      ],
      tracesSampler: (samplingContext) => {
        const transactionOp = samplingContext.transactionContext.op;
        if (transactionOp === 'navigation') {
          return 0.1;
        }
        return 1;
      },
      beforeBreadcrumb: (breadcrumb, hint) => {
        if (
          breadcrumb.category === 'console' ||
          (breadcrumb.category === 'xhr' &&
            breadcrumb?.data?.url?.includes('http://localhost:8081/')) ||
          (breadcrumb?.data?.status_code >= 200 &&
            breadcrumb?.data?.status_code < 300)
        ) {
          return null;
        }
        return breadcrumb;
      },
      _experiments: {
        profilesSampleRate: 1.0,
      },
    });

krystofwoldrich · 2024-09-13T11:35:39Z

@vinayak-bm-ai Thank you for the init options, we will investigate it.

VinhTruong2001 · 2024-10-04T03:44:36Z

Any new updates ? app keep crashing in production now

markushi · 2024-10-04T06:20:33Z

@vinayak-bm-ai thanks for sharing all the details. Unfortunately I still don't see how this issue is related to sentry.
Yes, there was a similar issue in combination with sentry in the past, but

libsentry.so was part of the stacktrace (which I don't see here)
it was fixed nearly a year ago

The root cause of the issue suddenly appearing out of nowhere could be the same though: a Google Play System update. So maybe it's worth checking which versions are installed on the affected devices.

Having said that, we've seen Profiling (the Android System Profiler used by the Android SDK) causing native crashes, if possible you could try to release a version with profilesSampleRate: 0.0 to see if it has any positive effect.

lucatomarelli · 2024-10-04T07:22:54Z

We managed to temporary fix the issue removing profilesSampleRate as @markushi suggests.

markushi · 2024-10-04T08:03:30Z

We managed to temporary fix the issue removing profilesSampleRate as @markushi suggests.

Glad to hear this helped!

It's worth mentioning that we've opened several bug reports and PRs to AOSP, to get this fixed in the long run, see this issue for more details.

If you can get hold of a detailed crash report, a tombstone or similar please share them with us, as this helps us tremendously!

markushi · 2024-10-04T08:07:44Z

Just to double check: @krystofwoldrich there's no known issue around native crashes due to RN profiling, right?

markushi · 2024-10-04T09:54:59Z

Quick update: This issue is actually a duplicate of getsentry/sentry-java#3653 The good news: The underlying Android issue was fixed already. The bad news: Unfortunately we don't know when/how Google will roll it out.

In the meantime we recommend disabling the Android native platform profiling, a feature we shipped in version 5.33.0 of the Sentry RN SDK:

import * as Sentry from '@sentry/react-native';

Sentry.init({
  integrations: [
    Sentry.hermesProfilingIntegration({ platformProfilers: false }),
  ],
});

We're keeping this issue open and will share any updates about the rollout.

krystofwoldrich · 2024-10-04T10:14:12Z

@markushi Just to double check: @krystofwoldrich there's no known issue around native crashes due to RN profiling, right?

Correct, there are no known crashes due to RN (Hermes) profiling.

vinayak-bm-ai added the Platform: React-Native label Sep 9, 2024

getsantry bot added the Waiting for: Product Owner label Sep 9, 2024

getsantry bot removed the Waiting for: Product Owner label Sep 10, 2024

getsantry bot added the Waiting for: Product Owner label Sep 10, 2024

getsantry bot removed the Waiting for: Product Owner label Sep 10, 2024

getsantry bot added the Waiting for: Product Owner label Sep 10, 2024

krystofwoldrich assigned markushi Sep 12, 2024

getsantry bot removed the Waiting for: Product Owner label Sep 13, 2024

getsantry bot added the Waiting for: Product Owner label Oct 4, 2024

getsantry bot removed the Waiting for: Product Owner label Oct 4, 2024

getsantry bot added the Waiting for: Product Owner label Oct 4, 2024

getsantry bot removed the Waiting for: Product Owner label Oct 4, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Android Crash: SIGSEGV 0x0000000000000000 - libc.so | Crashed: null pointer dereference #4075

Android Crash: SIGSEGV 0x0000000000000000 - libc.so | Crashed: null pointer dereference #4075

vinayak-bm-ai commented Sep 9, 2024 •

edited by krystofwoldrich

Loading

krystofwoldrich commented Sep 10, 2024

krystofwoldrich commented Sep 10, 2024

vinayak-bm-ai commented Sep 10, 2024

markushi commented Sep 10, 2024

vinayak-bm-ai commented Sep 10, 2024

vinayak-bm-ai commented Sep 10, 2024 •

edited

Loading

krystofwoldrich commented Sep 13, 2024

VinhTruong2001 commented Oct 4, 2024

markushi commented Oct 4, 2024

lucatomarelli commented Oct 4, 2024

markushi commented Oct 4, 2024 •

edited

Loading

markushi commented Oct 4, 2024 •

edited

Loading

markushi commented Oct 4, 2024

krystofwoldrich commented Oct 4, 2024

Android Crash: SIGSEGV 0x0000000000000000 - libc.so | Crashed: null pointer dereference #4075

Android Crash: SIGSEGV 0x0000000000000000 - libc.so | Crashed: null pointer dereference #4075

Comments

vinayak-bm-ai commented Sep 9, 2024 • edited by krystofwoldrich Loading

🛑 Blocked by getsentry/sentry-java#3653

Description

Steps to reproduce

React Native Version

Affected Platforms

Output of npx react-native info

Stacktrace or Logs

Reproducer

Screenshots and Videos

krystofwoldrich commented Sep 10, 2024

krystofwoldrich commented Sep 10, 2024

vinayak-bm-ai commented Sep 10, 2024

markushi commented Sep 10, 2024

vinayak-bm-ai commented Sep 10, 2024

vinayak-bm-ai commented Sep 10, 2024 • edited Loading

krystofwoldrich commented Sep 13, 2024

VinhTruong2001 commented Oct 4, 2024

markushi commented Oct 4, 2024

lucatomarelli commented Oct 4, 2024

markushi commented Oct 4, 2024 • edited Loading

markushi commented Oct 4, 2024 • edited Loading

markushi commented Oct 4, 2024

krystofwoldrich commented Oct 4, 2024

vinayak-bm-ai commented Sep 9, 2024 •

edited by krystofwoldrich

Loading

Output of `npx react-native info`

vinayak-bm-ai commented Sep 10, 2024 •

edited

Loading

markushi commented Oct 4, 2024 •

edited

Loading

markushi commented Oct 4, 2024 •

edited

Loading