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]: Eating up RAM #145

Open
1 task done
danblae opened this issue Feb 14, 2023 · 4 comments
Open
1 task done

[Bug]: Eating up RAM #145

danblae opened this issue Feb 14, 2023 · 4 comments
Labels
bug Something isn't working needs reproduction

Comments

@danblae
Copy link

danblae commented Feb 14, 2023

What happened?

When running the farmer on docker for a while it starts eating up the RAM. It took about 4 days to go up to 2.5gb of RAM

What should happen?

The RAM usage should stay low. A restart did the trick. Maybe an automatic restart of the browser session once in a while would help to keep the RAM down. My guess is, that cloudscrapper due to its JavaScript capabilities is eating the RAM.

Capsule Farmer Version

v1.3

Operating System

Windows 10

Operating System Version

Docker

Relevant log output

Not necessary

Notes

No response

My issue is not a question

  • I acknowledge that this issue is not a question or feature request.
@danblae danblae added the bug Something isn't working label Feb 14, 2023
@LeagueOfPoro
Copy link
Owner

It might be a Docker issue. I am running v1.3 without restart since it came out and its RAM usage with 6 accounts after 4 days is ~120 MB. The VPS has 1 GB RAM total.

@Ancient77
Copy link

Docker, especially Docker for Windows, is known to use a lot of RAM, try switching to wsl 1 or switching to Linux altogether.

@danblae
Copy link
Author

danblae commented Feb 14, 2023

It is running on Docker on a highly modified Debian. And it is not docker using the resources. It is the container.
I know Docker for Windows is eating a lot of resources. It is also not a huge deal and since you can not reproduce it, it does not really matter too much. I just thought it might be an issue for everyone running it on some server, that is not constantly monitored.

@danblae
Copy link
Author

danblae commented Feb 15, 2023

Feel free to close the issue if you want, I think this might be very low priority. My guess of what the issue is is out of your control. the only way to prevent it is to restart the cloudscraper instance in the code. I unfortunately do not have time to do a pull request where I properly tested the fix, but it should be rather straight forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs reproduction
Projects
None yet
Development

No branches or pull requests

4 participants