How do Kotlin coroutines behave during JVM safepoints and GC pauses?

Coroutines are paused indirectly during JVM safepoints and GC because threads are halted at execution points.

The JVM periodically introduces safepoints where all application threads are paused for GC, deoptimization, or class unloading. Kotlin coroutines do not bypass this because they run on JVM threads. When a safepoint occurs, all running coroutines are paused regardless of their state. This can cause latency spikes in coroutine-heavy systems, especially when GC is frequent due to allocation-heavy code. The coroutine scheduler resumes execution after safepoint completion.