New experimental feature and some fixes

[akornich]

New experimental feature and some fixes

• feat: Detection of possible Out-of-Memory issues
• fix: resolve v2.2.4 spams to log with NSLog on iOs #166 - v2.2.4 spams to log with NSLog on iOS
• fix: resolve Rollbar crashes when device runs out of memory #176 - Rollbar crashes when device runs out of memory
• fix: resolve SonarCloud: address current reliability issues #180 - SonarCloud: address current reliability issues

Special Release Note

In this upcoming v 2.3.0 release, we are adding a new experimental feature that detects Out-of-Memory (OOM) application crashes.

Due to the non-deterministic nature of the algorithm used for this, we expect a reasonable number of false-positive detection results. The algorithm is based on the exclusion of other reasons that may have forced an application to terminate until an OOM cause is left as the only very last suspect. Unfortunately, some system APIs used to exclude other causes of application termination are not completely reliable and could result in the false positive outcomes mentioned above.

We expect the actual frequency of these false positives to vary widely based on the concrete runtime environment including device, device model, device configuration, specific *OS, specific *OS version, and app usage profile.

We have the OOM detection FALSE by default; however, if you would prefer to turn it on you can set loggingOptions.enableOomDetection flag to TRUE when setting up RollbarConfig instance.

In the medium term, we have other improvements on the roadmap that would allow us to reduce (if not completely eliminate) false positives within the next few development iterations.

Let us know what you think about this new feature and how we can improve the SDK.

Thank you for using Rollbar!

---

This discussion was created from the release New experimental feature and some fixes.