Skip to content
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

Add additional app launch scenarios for OOM tracking #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rahul-malik
Copy link

Summary:
OOM tracking is based off of the blog post from Facebook https://code.fb.com/ios/reducing-fooms-in-the-facebook-ios-app/

This requires a process-of-elimination to determine if a launch is due to an OOM crash by marking every legitimate reason that an application could start. The article did not cover ways that the app may be launched from the OS which are background fetches and silent push notifications currently.

New additions in this PR

  • Track app launches for silent notifications and background fetch
  • Don't report OOMs if the previous session was for these reasons.

Summary:
OOM tracking is based off of the blog post from Facebook https://code.fb.com/ios/reducing-fooms-in-the-facebook-ios-app/

This requires a process-of-elimination to determine if a launch is due to an OOM crash by marking every legitimate reason that an application could start. The article did not cover ways that the app may be launched from the OS which are background fetches and silent push notifications currently.

  New additions in this PR
  - Track app launches for silent notifications and background fetch
  - Don't report OOMs if the previous session was for these reasons.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant