Crash in PlayServicesDevicePerformance BlockingCoroutine.joinBlocking [401465380]

Assigned

Bug

Status Update

No update yet.

Description

mi...@viber.com

created issue #1

Mar 7, 2025 02:39PM

Component used: androidx.core:core-performance-play-services

Version used:1.0.0

Devices/Android versions reproduced on: Many different devices and OS

After core-performance-play-services integration we see new crash affecting our users. We could not reproduce it by ourselves, just have stacktrace from crashlytics:

Fatal Exception: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:566)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1038)
Caused by java.lang.reflect.InvocationTargetException:
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:556)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1038)
Caused by java.lang.InterruptedException:
       at kotlinx.coroutines.BlockingCoroutine.joinBlocking(BlockingCoroutine.java:94)
       at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(BuildersKt__Builders.kt:69)
       at kotlinx.coroutines.BuildersKt.runBlocking(Builders.kt:1)
       at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(BuildersKt__Builders.kt:47)
       at kotlinx.coroutines.BuildersKt.runBlocking$default(Builders.kt:1)
       at androidx.core.performance.play.services.PlayServicesDevicePerformance$updatePerformanceStore$1.invoke(PlayServicesDevicePerformance.kt:106)
       at androidx.core.performance.play.services.PlayServicesDevicePerformance$updatePerformanceStore$1.invoke(PlayServicesDevicePerformance.kt:105)
       at androidx.core.performance.play.services.PlayServicesDevicePerformance.updatePerformanceStore$lambda$1(PlayServicesDevicePerformance.kt:105)
       at com.google.android.gms.tasks.zzm.run(com.google.android.gms:play-services-tasks@@18.1.0:1)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:211)
       at android.os.Looper.loop(Looper.java:300)
       at android.app.ActivityThread.main(ActivityThread.java:8322)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:556)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1038)

Comments

al...@google.com <al...@google.com> #2Mar 18, 2025 02:01PM

Reassigned to es...@google.com.

Routing per go/androidx/owners for insets.

es...@google.com <es...@google.com> #3Mar 18, 2025 02:21PM

Reassigned to nc...@google.com.

Hi @jb...@google.com,

Do you mind checking why FragmentContainerView still calls ViewCompat.dispatchApplyWindowInsets when the OnApplyWindowInsetsListener set to it always returns the consumed insets as here?

I also found that FragmentContainerView.kt:210 doesn't call ViewCompat.dispatchApplyWindowInsets but FragmentContainerView.kt:207 does. Not sure if the version was really androidx.fragment.fragment 1.8.6 from the stack trace.

nc...@google.com <nc...@google.com> #4Mar 19, 2025 09:54PM

Not sure, FragmentContainerView doesn't have that kind of control and just hands off to the core functions. Also the lines not matching up does likely mean the version are off. Can we get a sample project that reproduces the issue and we can have a closer look?

nc...@google.com <nc...@google.com> #5Mar 19, 2025 10:23PM

Hi enxyox@,

Do you know if this can happen on Pixel devices or emulators which run Android 8.0.0? If so, do you mind sharing a sample app for us to reproduce and investigate?

mi...@viber.com <mi...@viber.com> #6Mar 20, 2025 08:08AM

I couldn't reproduce this myself on an emulator running Android 8.0.0, so I only have stack traces from Crashlytics/Sentry. We've now gathered a bit more data, and the crash also occurs on Android 9.0 on the S119 device, though the majority (96%) is still on Android 8.0.0.

Some users experienced the crash when switching fragments (navigating to another screen), some right upon opening the app, and others when changing configuration. I can say for sure that this happens under rare conditions, as in our case, it has affected about 14% of users on Android 8.0.0.

nc...@google.com <nc...@google.com> #7Mar 20, 2025 03:11PM

Thanks, I have some ideas on a fix.

Issue 401465380