Detecting OOM terminations
Users say "the app just closes," but Crashlytics has nothing. If you suspect out-of-memory (OOM) terminations, how do you confirm it and gather data?
Users say "the app just closes," but Crashlytics has nothing. If you suspect out-of-memory (OOM) terminations, how do you confirm it and gather data?
An OOM is the kernel (jetsam) killing the process, so the crash handler never gets to run. You collect it from MetricKit's MXAppExitMetric and memory metrics and Xcode Organizer's Terminations, and reproduce it with Allocations.
Performance and debuggingShort answerBasics
You get an alert that crashes spiked in the version you shipped yesterday. What do you…
#crashlytics
Performance and debuggingShort answerAdvanced
A photo editing app gets frequent memory warnings and sometimes gets killed. In what…
#memory
Performance and debuggingShort answerBasics
Because of deep links or state restoration you have to push dozens of view controllers…
#memory
Performance and debuggingShort answerAdvanced
Besides retain cycle leaks, what other kinds of memory bugs do you run into on iOS? And…
#memory