4/2/2026 at 12:01:27 PM
by darccio
4/5/2026 at 4:42:25 PM
Interesting to see an ebpf approach to this idea, some time ago I did the same with Dtrace: https://gaultier.github.io/blog/detecting_goroutine_leaks_wi...However I did not think of observing the ‘castgstatus’ runtime function.
Always nice to be able to compare the DTrace and Ebpf approaches, they both have different strong points.
by broken_broken_
4/5/2026 at 5:13:36 PM
that is actually sick.how common is it for go devs to experience leaking goroutines ? id like to think go is a lot less shoot yourself in the foot here since they provide a framework for concurrency/parallelism rather than you working with the tiny pieces of it and building out the architecture yourself, but ive only needed to use goroutines once and it was a pretty problem-free experience.
by trueno
4/5/2026 at 8:35:37 PM
> how common is it for go devs to experience leaking goroutinesAbout as often as leaking memory in C++
by usrnm
4/5/2026 at 4:38:07 PM
Cool! is there something similar for async rust ?by xtoilette
4/5/2026 at 7:53:38 PM
https://docs.rs/tokio-console/latest/tokio_console/ comes to mind.I'm not aware of eBPF-based dynamic instrumentation for either tokio or other async runtimes, but I'm also not (in need to be) debugging this on a daily basis.
by fch42
4/5/2026 at 4:54:37 PM
So cool! Does it support multiple Go versions?by tsuzu
4/5/2026 at 7:18:28 PM
[dead]by darshil2023