问题描述
我通过增长无限大的NSString NSArray创建了OOM崩溃，甚至尝试调用exit(0)只是使其看起来像一个OOM.尽管这些事情可以使应用程序意外终止，但我在Crashlytics上看不到任何OOM的报告，并且在下次运行该应用程序时也未调用委托回调crashlyticsDidDetectReportForLastExecution:.我正在未连接模拟器的真实设备上运行该应用程序，并且报告了其他任何类型的崩溃/错误.有谁知道这个问题可能是什么?
I've created OOM crashes by growing an infinitely large NSArray of NSStrings, and I've even tried calling exit(0) just to make it look like an OOM. While these things to have worked to terminate the app unexpectedly, I don't see any OOMs reported on Crashlytics and it doesn't call the delegate callback, crashlyticsDidDetectReportForLastExecution:, on the next run of the app. I'm running the app on a real device that is not connected to a simulator, and any other kind of crash/error it reports fine. Does anyone have any idea what the issue might be?
推荐答案
Fabric的Mike在这里.我们也讨论了Fabric支持，但需要澄清所有问题. OOM是在服务器上检测到的，但会在当前UTC日结束时进行批量处理，并且在处理完成后的下一个UTC日开始，将在Fabric Crashlytics的仪表板中显示该OOM.
Mike from Fabric here. We chatted over Fabric support as well, but to clarify for all. OOMs are detected on the server, but are processed in batch at the end of a current UTC day and will be visible in your Fabric Crashlytics' dashboard starting the next UTC day after our processing completes.
这篇关于Crashlytics没有报告任何前台OOM的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！