The Silent Killer That’s Crashing Your Coroutines
<p>Today the production servers stopped responding to traffic again.</p>
<p>Last week, you just restarted them and wrote it off as a glitch. You couldn’t shake the feeling there was something weird about it, though. There wasn’t a trace of an error in the logs — not even a warning. Sure enough, the pattern this time is exactly the same.</p>
<p>One by one, the servers have gone into zombie mode. The lights are on, but nobody’s home.</p>
<p>Sounds like a nightmare scenario, right? But it’s exactly the kind of thing that can happen to your Kotlin coroutines when cancellation exceptions go rogue. And when cancellation exceptions are everywhere, the chances of that happening are higher than you’d think. Something as simple as calling <code>await</code> on a cancelled task can have counterintuitive and harmful results.</p>
<p><a href="https://betterprogramming.pub/the-silent-killer-thats-crashing-your-coroutines-9171d1e8f79b"><strong>Read More</strong></a></p>