alexriosme.substack.com/p/engineers-...

Five ways to leak a goroutine.

Not theory. Real bugs from CockroachDB, Kubernetes, etcd, and gRPC that shipped to production.

Part 3 of my series on Go's new leak detector.

alexrios.me/blog/gorouti...

Got feedback: my goroutine-leak series was too dense. Fair.

So I wrote Part 0: A gentler intro.

Core idea: spawn a goroutine, you become a parent. Leave before your child can finish? You've abandoned them. Forever.

That's a goroutine leak. And Go has no goroutine GC.

alexrios.me/blog/gorouti...

Standard profiling only gets you so far.

Part 2 of my Goroutine Leak Detection series is out, and this one hits hard. 🥊

I'm diving into the "GC Trick", using the runtime against itself to find the leaks that pprof misses.

Check it out: alexrios.me/blog/gorouti...

🧵 Go 1.26 introduces an experimental goroutine leak detector.

I spent weeks diving into the implementation, research papers, and real-world bugs it catches.

Here's what I learned (Part 1/4):
alexrios.me/blog/gorouti...

#golang #go

Stop lying to yourself about those _ = functionCall() patterns in your Go tests.
The underscore isn't a design decision. It's a white flag.

New post: alexrios.me/blog/a-confe...

#golang #testing

Privyet

Hello!

Today at 7pm in the Golang SP community I'm going to present the talk that happened at GolangConf 2025 X 🇷🇺.

This talk will be presented in portuguese 🇧🇷

(link in the comments)