kotlin-coroutines

Fix Kotlin coroutine memory leaks by scoping asynchronous work to viewModelScope or lifecycleScope, ensuring structured concurrency prevents leaked coroutines during screen rotation. Replace GlobalScope misuse with lifecycle-aware scopes to automatically cancel orphaned jobs and stop memory leaks.

Android app jank occurs when Kotlin coroutines block the main thread with network calls, requiring proper dispatcher selection to offload IO work. Use Dispatchers.IO for network requests and design main-safe suspend functions to prevent UI freezing.

The best way to model UI state with Kotlin Flow is using StateFlow for synchronous UI rendering and SharedFlow for one-shot events. This approach correctly handles asynchronous stream modeling and lifecycle compliance within Android ViewModels.

Yes, this coroutine debugging approach works with Kotlin 2.1+ and kotlinx.coroutines 1.9+, specifically targeting Android projects to enforce structured concurrency, cooperative cancellation, and proper exception handling standards.

Convert legacy callback APIs to Kotlin coroutines using suspendCancellableCoroutine, ensuring you properly propagate CancellationException instead of swallowing it. This prevents unhandled cancellations and maintains cooperative cancellation discipline during API bridging.

You should not use GlobalScope for Kotlin coroutines in Android when operations are tied to lifecycle components, as it breaks structured concurrency and causes memory leaks. Use viewModelScope or lifecycleScope to ensure automatic cancellation and proper exception handling.