A huge amount of OOM events

[kolyan94]

Environment

How do you use Sentry?

• Sentry SaaS (sentry.io)

Which SDK and version?

• "@sentry/react-native": "3.2.10"

Steps to Reproduce

We getting a huge amount of "The OS most likely terminated your app because it overused RAM." events (part of them were from a simulator). We didn't find any issue with RAM, but fortunately found one easy way to reproduce it (may not that triggers most of the events):

1. Launch the app from the Home screen
2. While the app is open try to build it through Xcode
3. When Xcode reopens the app we should get a new OOM event.

We don't think that this way is the main one, but unfortunately, we found only this one =(

Expected Result

These events shouldn't trigger.

Actual Result

We got a huge amount of OOM events

Similar issues: #1830 #1338

[jennmueng]

@philipphofmann

[Rubon72]

in my case app is not crushed, just a sentry error on the page with couple of requests and couple images, simular to category page

[namvoeh]

I got bunch of crash events on production as well, I could re-produce it by killing the app then reopen

[philipphofmann]

Can also reproduce this for sentry-cocoa. Going to move this.

[numandev1]

I am also using the same version and have the same issue. "@sentry/react-native": "3.2.10"

[philipphofmann]

When there is no debugger attached and you click run in Xcode for an already running app, Xcode kills the app and the SDK thinks it is an OOM. Checking previousAppState.isDebugging or the previousAppState wouldn't work, because the debugger is not attached. Ideally, we should find a way to know if Xcode killed the app.

[philipphofmann]

We also get false OOMs for our UI tests in Saucelab. Maybe this is related.

[github-actions[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[TomasSestak]

happens on 3.2.13 version, could it be by defining tracesSampleRate in options of init function? or by adding package date-fns ?

[philipphofmann]

The tracesSampleRate has no impact on OOM events. You can use beforeSend to drop OOMs events if you want, @TomasSestak.

[TomasSestak]

The tracesSampleRate has no impact on OOM events. You can use beforeSend to drop OOMs events if you want, @TomasSestak.

Thanks for clarification. In our case it crashes the app so I will try to debug it somehow

[philipphofmann]

@TomasSestak, @numandev1, @namvoeh, @kolyan94, we didn't see any updates for a long time on this issue, and we did plenty of fixes for OOM. I consider this to be fixed. Please reopen the issue or create a new one if you still experience problems.