By adding an SDK callback, you can obtain the records captured by the SDK when a suspected OOM occurs. This callback is executed only when "Whether to report only confirmed OOM crashes" is configured as "Yes" in the SDK reporting configuration. Through this callback, you can obtain suspected OOM crash logs that were not reported, and you can perform statistics through methods such as instrumentation or by using logs as needed.

/**​
Set the suspected OOM crash callback. Triggered when the SDK determines a possible OOM after ruling out causes such as watchdog and ordinary crashes.​
Note:​
1. Set it before initializing APM (i.e., before calling +[RangersAPM startWithConfig:]) to ensure it takes effect on the first launch.​
2. The callback may be triggered on a non-main thread. Avoid performing time-consuming operations or anything that requires the main thread.​
3. If only "confirmed OOM" is reported (configured in the APMPlus console), suspected OOM will only be returned through this callback and will not be uploaded.​
 ​
 Set the callback for suspected OOM crash. It fires when the SDK considers a possible OOM after excluding watchdog and regular crashes.​
 Notice:​
    1. Set this before initializing APM (before calling +[RangersAPM startWithConfig:]) to take effect from the first launch.​
    2. The callback may be invoked off the main thread; avoid heavy work or main-thread-dependent operations inside it.​
    3. If only “certain OOMs” are uploaded (APMPlus console configuration), non-certain OOMs will be returned via this callback without uploading.​
 */​
+ (void)setMaybeOOMCrashCallback:(RangersAPMOOMCrashCallback)callback;​

Last updated: 2026.10.23 11:17:27

Public security network record in Beijing: No. 11010802032137