Skip to content
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

Backport of VAULT-4240 time.After() in a select statement can lead to memory leak into release/1.9.x #14824

Merged

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #14814 to be assessed for backporting due to the inclusion of the label backport/1.9.x.

The below text is copied from the body of the original PR.


The time.After call in the for - select statement can lead to a memory leak because the garbage collector does not cleanup the underlying Timer object until the timer fires. A new timer is initialized at each iteration of the for loop (and hence select), which requires resources. So, many routines originating from the time.After call could lead to overconsumption of the memory.

@hghaf099 hghaf099 merged commit 689e51e into release/1.9.x Apr 1, 2022
@hghaf099 hghaf099 deleted the backport/leaky-timeAfter/loudly-cunning-albacore branch April 1, 2022 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants