At 3:17 AM on a Tuesday in Q3 2024, our production Kotlin 2.0 microservice fleet hit a 92% memory utilization threshold across 140 nodes, traced to a silent coroutine leak in Ktor 2.2’s request pipeline that had been bleeding 12MB of heap per second for 72 hours. We lost $14k in SLO credits before we found the root cause. 📡 Hacker News Top Stories Right Now A Couple Million Lines of Haskell: Production Engineering at Mercury (78 points) Clandestine network smuggling Starlink tech into Iran to beat internet blackout (36 points) This Month in Ladybird - April 2026 (181 points) Six Years Perfecting Maps on WatchOS (199 points) Dav2d (364 points) Key Insights Ktor 2.2’s default CoroutineDispatcher retains cancelled request scopes for 30s beyond timeout, leaking 1.2k coroutines per 10k requests under load Kotlin 2.0’s new coroutine debugger (part of kotlinx-coroutines-debug 1.8.0) reduced root cause identification time from 14 hours to 47 minutes Fixing the leak cut monthly infrastructure costs by $18,300 across…