Crashlytics has released a new feature to report out of memory (OOM) crashes.
We all know regular crashes - termination of an app due to some code (app or system libraries).
OOM is another type of crash, which has been ignored in Crashlytics reports until now.
There are 2 types of OOM crashes:
- Foreground OOM (FOOM) - this crashes like regular crashes
- Background OOM (BOOM) - app is evicted from iOS
The method to detect OOM is first introducted by Facebook, using a process of elimination.
Crashlytics has provided reporting on OOM-free sessions.
Specifically, that is a percentage of sessions that are crash free from FOOM. Note: This is only for FOOM (Foreground OOM), since FOOM are similar to regular crashes while the app is in the foreground.
Also, the number of sessions in Answers does NOT include OOM sessions that crashed.
Crashlytics thrives in providing analytics to crashes, and the inclusion of OOM crashes will be very useful.
Some pointers on debugging and fixing these memory issues is provided.