tests: hashmap optimize memory usage #1780
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've noticed that test(s) in
github.com/ssvlabs/ssv/utils/hashmap
package consume up to 8GB of memory when running, sometimes it even results in the test being killed by OS:There seems to be a memory leak (creating
Timer
objects in almost infinite loop that is forcefully broken by Test terminating its run). This PR fixes it, and cleans up a bit.I've also checked all other places in this repo that could have had similar issues (when combining
for{}
,select
,time.After
) and found only 1 other test affected by this: #1781