Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production

Re:Finding and Fixing a 50k Goroutine Leak That Nearly Kille... by LatencyKills on Saturday January 17, 2026 @08:33AM (#46657942)

I do have expertise in Go. The bug was real, and the fix makes sense (though I couldn't verify it, of course).

I just hope HN gets over the "but it might be AI!!" crap sooner rather than later and focuses on the actual content because these types of posts are never going away.

[ Parent | on HN ]

Re:Finding and Fixing a 50k Goroutine Leak That Nearly Kille... by tim-kt on Saturday January 17, 2026 @08:45AM (#46658020)

Personally, I just don't like the way this is written. As I said though, I am not an expert and so I may be outside the target group. I think that the original "this is AI" comment is an automatic response which alternatively carries the meaning "this is low-effort" and in that sense I still think that it is valid criticism.

[ Parent | on HN ]

Re:Finding and Fixing a 50k Goroutine Leak That Nearly Kille... by LatencyKills on Saturday January 17, 2026 @08:56AM (#46658090)

Fair enough - I appreciate your thoughts. I'll keep the "this is low-effort" == "this is AI" equivalence in mind moving forward.

[ Parent | on HN ]

Re:Finding and Fixing a 50k Goroutine Leak That Nearly Kille... by vuciuc on Saturday January 17, 2026 @11:35AM (#46659364)

Even the part where they deploy new code to production without restarting processes?

[ Parent | on HN ]

Re:Finding and Fixing a 50k Goroutine Leak That Nearly Kille... by ilogik on Saturday January 17, 2026 @10:01AM (#46658575)

I've done a similar fix, even a bit more interesting, however I wouldn't consider it worthy of writing a blog post, not to mention submitting it to HN.

[ Parent | on HN ]