-
-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use memory pressure info for watchdog terminations #3890
Labels
Comments
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As described in #2514 and #3870, we could potentially use the dispatch queue's memory pressure information to report watchdog terminations as OOMs. However, we still need to determine how reliable this information is. It's highly likely that it won't work for big increments in memory consumption, for which the watchdog quickly kills the app process, and the app has no time to receive memory pressure information. It could be that this information is useful for OOMs that slowly creep in and eat up the memory. Anyways, if we report OOMs, we need to be sure that there is one; otherwise, it will be confusing to users. Another option is to somehow identify watchdog termination events with high memory pressure in Sentry. Adding breadcrumbs isn't enough because they aren't searchable/filterable in the product.
The text was updated successfully, but these errors were encountered: