android-coroutine-trace

To diagnose stuck Kotlin coroutines in your Android app, install DebugProbes in Application.onCreate to observe coroutine state and suspension points, then dump active coroutines to identify the root cause.

A coroutine continuing after screen navigation indicates a leaked job. Dumping active coroutines with DebugProbes helps identify these leaked jobs and duplicate launch points that outlive the ViewModel scope.

To find a flow collect that never completes, use kotlinx-coroutines-debug to snapshot active coroutines. This identifies the exact suspension points where the flow is stuck and guides the fix.

Yes, kotlinx-coroutines-debug can fix memory leaks caused by coroutines. It snapshots active coroutines to identify leaked jobs and suspension points causing memory creep, after which you apply fixes and remove the instrumentation.

The best way to inspect suspension points in Android coroutines is installing DebugProbes in Application.onCreate. It observes coroutine state and provides dumps to pinpoint exactly where suspending flows are stuck.

You should remove DebugProbes from your Android application after validation is complete. The instrumentation is temporary for diagnosing coroutine leaks and hangs, so remove it once fixes are applied.