(ios only) codepush.restartApp triggers invalid OutOfMemory errors

[savv]

Environment

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

Which SDK and version? "@sentry/react-native": "3.1.1",

Steps to Reproduce

Our app is generating OutOfMemory The OS most likely terminated your app because it overused RAM. errors since upgrading to 3.1.1. We were previously on 2.4.2. The Podfile.lock shows that Sentry/Core (= 7.3.0) is installed. It previously showed: Sentry/Core (= 6.1.4).

The same logs show that there's plenty of memory to go around, on some devices:
Memory Size 5.6 GiB
Usable Memory 3.9 GiB

Expected Result

These errors shouldn't trigger.

I also posted about this here, but perhaps this issue should be reopened?
#1633
getsentry/sentry-cocoa#1185

Thanks

[marandaneto]

cc @philipphofmann do you know if there's any issue above sentry cocoa > 6.1.4?

maybe related to getsentry/sentry-cocoa#1338

[philipphofmann]

@savv, do you get these false OOMs only in debug or also in a release build?

[savv]

@philipphofmann , thanks for responding. I am only getting those in our release build (we disable sentry on dev builds).

[philipphofmann]

@savv, can you please share your Sentry config with us, please? Of course without the DSN.

[savv]

Hi @philipphofmann , in the process of replying here (and adding comments & example values for environment, release, dist, etc), I realised that this issue stopped appearing with our latest release.

The only thing that changed between those two releases was react-native-reanimated@2.3.0-beta.2. We downgraded it to 2.2.3 because the beta version was causing other issues, and it seems that those versions don't have the OOM error anymore. So that may be a good path to a minimal repro.

In the meantime, we could keep this open and I can report back whether this still happens in a week, after some further testing?

[savv]

And while I have your attention. Thank you Sentry for making such an excellent product!

[philipphofmann]

Thanks for the lovely feedback, @savv. I hope you have good news for us in a week.

[vincent1114]

Same here,
We upgraded from 2.4.3 to 3.1.1 and getting a lot of OOM errors when our app wasn't using too much ram (around 50mb).
react-native-reanimated version was 2.1.0

[kieran-osgood]

I don't wanna hijack the issue or assume its the same thing, as I haven't 'recently' upgraded from one version to the next and noticed a difference, but I am experiencing a number of OOM errors whilst still seemingly having a lot of memory available, appears to be iOS only, and this happens in both debug and release modes. Having said that, I also tried to downgrade back to sentry 2.4.2 and was still experiencing crashes.

These crashes seem to happen arbitrarily, e.g. I could leave the app on what is my login screen, so really not doing any nor having had any business logic involved or interactions, and after 15-20 minutes it could crash. Can't say I saw anything related to sentry in the error output but some of them had seemed to indicate react-native-reanimated e.g.
The main issue has been:

OutOfMemory
The OS most likely terminated your app because it overused RAM.

But also receiving

EXC_BAD_ACCESS: , category =  > OOM: error_code(value = 1, category = vm_allocate_category, message = Max heap size was exceeded) > vm_allocate_category >
Stack overflow in _ZN8facebook3jsi16RuntimeDecoratorINS0_7RuntimeES2_E4callERKNS0_8FunctionERKNS0_5ValueEPS8_m

and

EXC_BAD_ACCESS: Exception 1, Code 8, Subcode 8 >
Attempted to dereference garbage pointer 0x8.

Trying to dig further to figure out what is causing these specifically as it may be unrelated I'm honestly not sure

[savv]

These errors appeared again, so my theory implicating react-native-reanimated now seems unlikely.

However, I am now able to reproduce these consistently, whenever the app installs a new Codepush bundle. I'm on "react-native-code-push": "7.0.3".

Calling codePush.restartApp(false); also triggers this.

[ryanseery]

I am currently experiencing the same error on "@sentry/react-native": "3.0.3". Podfile.lock shows Sentry/Core (= 7.3.0) is installed. Logs are also showing that there is plenty of memory:
Memory Size: 5.6 GiB
Usable Memory: 3.7 GiB

[awinograd]

I'm seeing the same erroneous errors on 3.1.1 (in a bare expo workflow). These OOM errors happen in our e2e detox tests when calling detox.reloadReactNative().

Appears to happen regardless of react-native-reanimated version.