Skip to content

[🐛 Bug]: Distributor and router pods do not release memory #2841

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

Open
DmiDvor opened this issue May 22, 2025 · 1 comment
Open

[🐛 Bug]: Distributor and router pods do not release memory #2841

DmiDvor opened this issue May 22, 2025 · 1 comment

Comments

@DmiDvor
Copy link

DmiDvor commented May 22, 2025

What happened?

Hi. Deployed a new version of Selenium Grid 4.32.0. Tested for several days. The distributor and router pods increase memory usage when starting new tests. But the memory is not released back when the tests are finished. Is the garbage collector not working?
Another question: if I deploy 2 pods for both the distributor and router, will it help to save fault tolerance? If one pod is stopped by OOM-killer, will the second pod continue the execution of what the first pod was doing?

Image

Command used to start Selenium Grid with Docker (or Kubernetes)

helm

Relevant log output

---

Operating System

k8s

Docker Selenium version (image tag)

4.32.0

Selenium Grid chart version (chart version)

0.43.2

Copy link

@DmiDvor, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant