Sentry-react-native: [iOS] OutOfMemory errors dont seem reliable on 2.5.2

Created on 24 Jun 2021  路  8Comments  路  Source: getsentry/sentry-react-native

Environment

How do you use Sentry?
Sentry SaaS (sentry.io)

Which SDK and version?
Sentry: 2.5.2
React native: 0.63.4
React: 16.13.1

Steps to Reproduce

I've upgraded to 2.5.2 and on iOS i keep seeing OutOfMemory exceptions on sentry, even from simulator sessions that i ran and know the app didn't crash and memory looked good. Also no crashes reported on appstore connect on firebase.

Type Bug iOMac Awaiting Fix

Most helpful comment

@RenatoSerra22 You can pass enableOutOfMemoryTracking: false to Sentry.init and it'll go through to iOS. Typescript will complain but it will go through nonetheless.

All 8 comments

Routing this to @philipphofmann, for reference here's this occurring from our sample app on a simulator that didn't crash: https://sentry.io/organizations/sentry-sdks/issues/2355695161/

Probably related to the cocoa bug https://github.com/getsentry/sentry-cocoa/issues/1185 , my heart almost exploded when i saw most of my users were "crashing" on a new release 馃槩

I'm deeply sorry about that, @RenatoSerra22. We are going to fix this. To stop your heart from exploding, maybe it's best to disable out-of-memory tracking for now.

@philipphofmann how to do that?
In our app, OutOfMemory error counts codepush upgrades on Sentry :D

i think enableOutOfMemoryTracking is not available on the initializer in react react native

@RenatoSerra22 You can pass enableOutOfMemoryTracking: false to Sentry.init and it'll go through to iOS. Typescript will complain but it will go through nonetheless.

@philipphofmann how to do that?
In our app, OutOfMemory error counts codepush upgrades on Sentry :D

You find the answer here: https://docs.sentry.io/platforms/apple/configuration/out-of-memory/ @ku8ar

After disabling OOMTracking, we went from thousands of errors to under ten, but we're still getting them nonetheless.

Not sure of the reporting mechanism, but is it possible for the following sequence of events to happen?

  1. OOM error captured
  2. User upgrades to version with OOMTracking disabled
  3. On app start, error gets shipped
  4. The error on the Sentry dashboard says the user was on the latest version of the app

We are disabling it on the native side in AppDelegate's didFinishLaunchingWithOptions.

Was this page helpful?
0 / 5 - 0 ratings