kotlin-concurrency-expert

Fix Kotlin coroutines memory leaks by enforcing structured concurrency and using lifecycle-aware scopes like viewModelScope, which automatically cancel background work when the ViewModel is cleared.

Structured concurrency in Kotlin Android ensures coroutines are launched in proper scopes, enforcing hierarchical cancellation and preventing orphaned background tasks from causing race conditions or lifecycle leaks.

Audit Android coroutine dispatchers by reviewing background work to ensure safe dispatching and testable usage, remediating improper dispatcher assignments that cause UI jank or race conditions across components.

Mis-scoped coroutines cause ANRs by running background work outside lifecycle-aware scopes, leading to blocked threads and memory leaks that freeze the UI and bypass structured concurrency cancellation.

Use lifecycleScope for Android background work tied directly to UI lifecycles, ensuring proper cancellation when the lifecycle owner is destroyed, while viewModelScope handles ViewModel-specific concurrent tasks.