Results
82
comments of
Ivan
trafficstars
Updating all dependencies and go version made it so I could no longer _quickly_ reproduce the memleak, but let's be careful, you never know with this things. I released 0.5.2...
All good on my end