bill-kotlin-code-review-platform-correctness

You can detect race conditions and coroutine leaks by applying a code review process that identifies improper dispatcher usage, unsafe state handling, and missing explicit cancellation to improve Kotlin application reliability.

Common Kotlin coroutine pitfalls include using GlobalScope, improper dispatcher selection, ignoring explicit cancellation, and unsafe state handling, which can cause coroutine leaks and race conditions during execution.

To enforce lifecycle-safe patterns for Kotlin coroutines, ensure explicit ownership of long-running operations, enforce explicit cancellation, and verify proper dispatcher usage to prevent leaks and threading issues.

Yes, this concurrency code review applies to Kotlin libraries, apps, and modules where lifecycle management, coroutine usage, or threading concerns are present, ensuring correctness across different project types.

Your Kotlin coroutine leaks memory during long-running operations likely due to missing explicit cancellation, improper lifecycle ownership, or using GlobalScope, which prevents coroutines from being properly cleaned up.