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

[NoDriver] performance decreases after sequentially created browser instances. #1883

Open
gnori-zon opened this issue May 13, 2024 · 1 comment

Comments

@gnori-zon
Copy link

gnori-zon commented May 13, 2024

That is, the first 5 instances will work faster than the next ones. This ultimately leads to dependencies and very slow performance.

If you stop and restart the docker container that is running, performance will improve, but after a while it will drop again. I think this is because there are zombie processes left (crome_crashpad, crome, cat) that are children from Python (application)

Scenario:

  • open 5...some work...close 5,
  • open 5...some work...close 5

Pls, tell me your guesses)

@montovaneli
Copy link

I don't know if it's an issue, but since the deconstruct_browser() function from core/util.py is being called only when the program exits, the __registered__instances__ set increases after every uc.start() and it doesn't decrease until the program exits. Also, the browsers' data dirs are being removed only when the program exits.

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

No branches or pull requests

2 participants