ANR on `Rum.enable()` about dd-sdk-android HOT 7 CLOSED

Thank you for the stack trace and the related information. We will add a ticket on our end to investigate this and keep you updated on this thread.

from dd-sdk-android.

Hi @0xnm , sorry for late reply

• Is stacktrace you are posting coming from Play Store?
  Yes, it's from Play Store
• Stacktrace from your original message has different methods involved compared to the second stacktrace you've posted (there are some methods in former which don't exist in the latter) - can you give an explanation for this one / post relevant stacktrace?
  Yes, stacktrace from Play Store are from specific user session, I probably copy-paste different one from the original message vs the second one.
• Do you see any pattern in your application version (and thus in our SDK version) / OS version / device for the ANRs you are getting?
  No pattern in Application Version.
  From 89% ANRs are from Android 11 OS

from dd-sdk-android.

Hi @fchristysen, thank you for taking the time for reporting this issue. I am afraid we will need more information from your end in order to better understand what is going on. Can you please provide us with the following information :

• a complete stack trace of the ANR error
• how often this happens, what are the devices model and maybe some scenario through which you are able to reproduce the issue ?

Thanks !!

from dd-sdk-android.

Hi @mariusc83, Thanks for quick reply.

a complete stack trace of the ANR error

com.traveloka.android.datadog.DatadogUtil.initializeRUM
Input dispatching timed out (No focused window)
  at com.datadog.android.rum.internal.RumFeature.createDataWriter (RumFeature.kt:241)
  at com.datadog.android.rum.internal.RumFeature.onInitialize (RumFeature.kt:142)
  at com.datadog.android.core.internal.SdkFeature.initialize (SdkFeature.java:89)
  at com.datadog.android.core.DatadogCore.registerFeature (DatadogCore.kt:134)
  at com.datadog.android.rum.Rum.enable (Rum.java:61)
  at com.datadog.android.rum.Rum.enable$default (Rum.java:35)
  at com.traveloka.android.datadog.DatadogUtil.initializeRUM (DatadogUtil.kt:107)
  at com.traveloka.android.AppTravelokaApplicationListener.lambda$setupDatadogSDK$7 (AppTravelokaApplicationListener.java:272)
  at rx.internal.util.ActionSubscriber.onNext (ActionSubscriber.java:39)
  at rx.observers.SafeSubscriber.onNext (SafeSubscriber.java:134)
  at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.call (OperatorObserveOn.java:224)
  at rx.android.schedulers.LooperScheduler$ScheduledAction.run (LooperScheduler.java:107)
  at android.os.Handler.handleCallback (Handler.java:938)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loop (Looper.java:264)
  at android.app.ActivityThread.main (ActivityThread.java:8315)
  at java.lang.reflect.Method.invoke (Native method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:632)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1049)

how often this happens, what are the devices model and maybe some scenario through which you are able to reproduce the issue?

Based on our play store metrics, 0.9% sessions of our users. We put our RUM.enable on our app startup, on our Application class onCreate.

from dd-sdk-android.

Hello @fchristysen! We have additional questions to continue our investigations:

• Is stacktrace you are posting coming from Play Store?
• Stacktrace from your original message has different methods involved compared to the second stacktrace you've posted (there are some methods in former which don't exist in the latter) - can you give an explanation for this one / post relevant stacktrace?
• Do you see any pattern in your application version (and thus in our SDK version) / OS version / device for the ANRs you are getting?

from dd-sdk-android.

Hi @fchristysen, sorry for the delay. We were not able to reproduce this issue on our end so far and we could not see it yet in our metrics. Looking in the provided stack trace I see that you are using RxAndroid and that you are initializing the Datadog SDK in a RX scheduler. The way I remember is that the stack traces in RX can be scattered due to the multi - threading chain of operation calls. I am wondering if this could be really caused by our SDK or it could be something else ? Is the initialize method called on a rx.android.schedulers.LooperScheduler running on the UI Thread ?

from dd-sdk-android.

Closing this because we did not get any reply from the reporter.

from dd-sdk-android.