New issue
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
Identify potential memory leaks in our goroutines using uber-go/goleak
#5373
Labels
good first issue
Issues identified as good for first-time contributors
proposal
An issue that proposes a feature request
ready for refinement
An issue that was triaged and it is ready to be refined
Comments
Hi @shaun-nx thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
shaun-nx
added
good first issue
Issues identified as good for first-time contributors
ready for refinement
An issue that was triaged and it is ready to be refined
labels
Apr 11, 2024
List of known goroutinesThis will be a list of which
Detailed list of known goroutines
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Issues identified as good for first-time contributors
proposal
An issue that proposes a feature request
ready for refinement
An issue that was triaged and it is ready to be refined
As a maintainer of the NGINX Ingress Controller, I would like to know if there are any potential memory leaks in our go routines.
UACs:
uber-go/goleak
in each test to identify a potential leakResources:
https://github.com/uber-go/goleak
https://medium.com/@hatronix/title-demystifying-gos-runtime-numgoroutine-93fddbb67527#:~:text=NumGoroutine()%20is%20a%20simple,the%20concurrency%20of%20your%20application.
The text was updated successfully, but these errors were encountered: