Firebase Crashlytics - OOM limitation

[Sahith-Symph]

I used FastImage in Flatlist in an un optimized way , After the crash has happened in the application , i am not able to see any crash in the firebase crashlytics dashboard , got to know that Firebase won't report OOM , but other tools like sentry and bugsnag can do , is there any recommended workaround for this OOM crashes .

[TrinaxCode]

For an iOS memory-limit (jetsam) termination, there often isn't a normal crash report for Crashlytics to upload: iOS can kill the process without giving it a chance to run app code. Firebase describes Crashlytics reports as crashes and non-fatal errors; Apple classifies memory-limit and memory-pressure stops as app terminations. So a missing Crashlytics issue does not by itself mean the OOM didn't happen.

For diagnosis, check Xcode Organizer's Terminations data or collect MetricKit's MXAppExitMetric. A jetsam event report can show the process's memory use and termination reason, but it does not contain an app backtrace. Reproduce on a real device and profile the long-scroll flow with Xcode's memory gauge/Instruments; the Simulator doesn't reproduce iOS OOM termination behavior.

For the FastImage + FlatList case, I'd first verify the actual decoded image sizes. Request thumbnails close to the rendered cell size instead of downloading full-resolution photos for every row, avoid preloading the entire list, and cap how many decoded images/concurrent loads are retained. Also handle memory warnings by releasing recreatable image/cache data, but treat warnings as best-effort: iOS may terminate the process before one arrives.

References: Crashlytics for Apple platforms, Reducing app terminations, low-memory warnings, and reducing memory use.

[Sahith-Symph]

Thanks for the detailed reply , will try to diagnose with your insights