DiagnosticEventProcessor.startScheduler causing OOM on certain devices

[repl-saijanani-s]

SDK version
3.1.1

Happened on different devices and different OS versions from Android 9-13 for multiple users.

[louis-launchdarkly]

Hello @repl-saijanani-s, thank you for reporting the issue to us.

I have a couple of follow-up questions for you on this one - Do you see this error for any later Android versions? Also, do you see any thread-related errors that happen with EventProcessor.start()? The name sounds similar but this one is for the analytics events that drive features you can use in LaunchDarklyUI. My suspicion is that older Android doesn't have enough memory for the few separate threads that the SDK allocates.

In terms of suggestions in the meantime, we recommend migrating to the latest Android 4.x SDK, and if you cannot migrate yet, you can turn off diagnostic events via SDK configuration. Turning diagnostic events off will not affect functionality in your LaunchDarkly UI.

Keeping track of this internally with 190650.

[github-actions]

This issue is marked as stale because it has been open for 30 days without activity. Remove the stale label or comment, or this will be closed in 7 days.