We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go-header/p2p/peer_tracker.go
Line 228 in 18f0eb1
defer ticker.Stop()
Kindly cc-ing @Wondertan @walldiss @liamsi
The text was updated successfully, but these errors were encountered:
True. Luckily, it runs once per node instance for a lifetime of application without any practical leaking.
A simple good first contribution to the lib
Sorry, something went wrong.
No branches or pull requests
go-header/p2p/peer_tracker.go
Line 228 in 18f0eb1
leaks the ticker due to a missing
defer ticker.Stop()
For an efficient p2p mechanism, let’s ensure that we gut out noise and RAM consumers like this. I’d suggest integrating static analyzers in the workflow and CI process. At Orijtech Inc we built a bunch of tools at https://cyber.orijtech.com/tools but for this case we produced tickeryzer https://medium.com/orijtech-developers/tickeryzer-static-analyzer-to-report-missing-time-ticker-stop-call-which-causes-resource-leak-2060a617a830Kindly cc-ing @Wondertan @walldiss @liamsi
The text was updated successfully, but these errors were encountered: