Suddenly getting many Fabric Out of Memory sessions: Can Fabric OOM Reports ever be false alarms?

Question

I recently added background fetch in my application and it is working well. I recently noticed in Fabric that the amount of OOM free sessions have gradually gone from 100% to a daily average steady in the teens as low as 14%. I only saw a few crashes reported here and there and there is no other evidence of crashes reported by users.

After reading how OOM sessions are detected, it seems like it may be false reports. Users launch the app and later it goes to background state. Then later, the app is launched for background fetch, performs fetches, and is terminated - this happens as often as the OS allows.

Is it possible that the Fabric's OOM detector is falsely detecting OOMs due to the way repeated background fetch launches and terminations happen?

Answer 1

Yes, there are certain instances when OOMs are falsely detected due to the current OOMs heuristics. Background fetching can falsely report OOMs.