A potential goroutine memory leak
xuxiaofan1203 opened this issue · 2 comments
Hello, I found a potential bug when I used the project, I'm not sure I'm right, we can discuss the problem to avoid a potential trouble possibly.
Blocking position:
client_golang/prometheus/registry.go
Line 472 in 26e3055
At line 449 call the wg.Add(goroutineBudget), and wg.Wait() is blocked until wg.Done() is called the number of goroutineBudget times to awaken the wg.Wait().
But if the select statement chooses the default path, return the function, maybe the wg.Done() has not executed enough times to awaken the wg.Wait(), which can result in a goroutine leak
client_golang/prometheus/registry.go
Lines 451 to 463 in 26e3055
Complete codes of the part
client_golang/prometheus/registry.go
Lines 449 to 475 in 26e3055
I guess we could test this behavior using the runtime package? More precisely, using runtime.NumGoroutine()
(https://pkg.go.dev/runtime#NumGoroutine)
Verify the number of goroutines, execute the function you believe there is a leak, and verify the number of go routines again. If numbers are different, it means we have a leak :)
As @kakkoyun suggested, we can double check with https://github.com/uber-go/goleak. Help wanted to add this (if not added before) (: