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

Bug Report Memory Leak #595

Open
xizheyin opened this issue Sep 12, 2024 · 2 comments
Open

Bug Report Memory Leak #595

xizheyin opened this issue Sep 12, 2024 · 2 comments
Assignees
Labels
bug Something isn't working Hacktoberfest2024 rust Pull requests that update Rust code

Comments

@xizheyin
Copy link

Mega occupies more than 30GB memory, which may be memory leak.
4bed13ef7d042d70e02d573fceeff2e
424f91344ad8f00b741f17042a3b424

@benjamin-747 benjamin-747 self-assigned this Sep 12, 2024
@benjamin-747 benjamin-747 added bug Something isn't working rust Pull requests that update Rust code labels Sep 12, 2024
@Hou-Xiaoxuan
Copy link
Contributor

Could you please provide more details on the steps to reproduce it? @xizheyin

Did the issue occur while pushing the repository to Mega, or while pulling from it? Or did it happen without any operation, with the memory usage continuously increasing?

@genedna
Copy link
Member

genedna commented Sep 13, 2024

@Hou-Xiaoxuan ,

I'm also experiencing the same issue. I downloaded all crates from crates.io, extracted them, initialized the extracted directory as a git repository, and then pushed it to the mega service. However, I noticed that Mega's memory usage did not decrease.

You can use the script in the crates-sync to test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Hacktoberfest2024 rust Pull requests that update Rust code
Projects
None yet
Development

No branches or pull requests

4 participants