Closed nicolas-lefloch closed 4 hours ago
@nicolas-lefloch, thank you for creating this issue. We will troubleshoot it as soon as we can.
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!
I saw
- name: SE_START_XVFB
value: "false"
Did you run the test with headless mode (arg --headless=new
) is used?
Thanks for your response, yes we use --headless=new
Let's starting it by setting to true
. I remember someone feedback that in new version, headless mode requires xvfb
Setting the SE_START_XVFB parameter to true worked perfectly.
Thank you for your quick help.
https://github.com/SeleniumHQ/docker-selenium/blob/trunk/README.md#running-in-headless-mode
What happened?
Context We use Selenium with the Python client on a self-hosted EKS grid. We are using a proxy to get out of our EKS cluster.
Problem When upgrading Chrome node to 127.0 we noticed a significant increase in CPU on these pods, which was accompanied by numerous execution failures "Could not start a new session. New session request timed out". It correctly works with node-chrome:126.0.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
EKS
Docker Selenium version (image tag)
node-chrome:127.0
Selenium Grid chart version (chart version)
No response