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

fix: resolve actix memory leak #2606

Merged
merged 2 commits into from
May 4, 2020
Merged

fix: resolve actix memory leak #2606

merged 2 commits into from
May 4, 2020

Conversation

bowenwang1996
Copy link
Collaborator

Pins actix-rt version 1.1.1 to fix the memory leak caused by actix/actix-net#129. Resolve #2593.

Test plan

Existing tests pass.

@gitpod-io
Copy link

gitpod-io bot commented May 4, 2020

@bowenwang1996 bowenwang1996 requested a review from frol May 4, 2020 13:56
@@ -39,6 +39,9 @@ members = [
"tools/restaked"
]

[dependencies]
actix-rt = "=1.1.1"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's have a comment right there with the link to the issue and some context, so it is immediately obvious why this was done. Do you think it makes sense to pin it instead of just requiring 1.1.1, which in semver means 1.1.1+?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense to pin the exact version for now. This is only intended to serve as a temporary solution. A longer term solution would be to update all the actix libraries when they update actix-rt version.

@bowenwang1996 bowenwang1996 merged commit 9ab4542 into master May 4, 2020
@bowenwang1996 bowenwang1996 deleted the fix-actix-memory-leak branch May 4, 2020 14:43
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.

Excessive memory usage on archival node
2 participants