A few days ago, for reasons that were inexplicable to me, the background work of selenium (via Xvfb) was accompanied by an automatic launch of an instance of chromedriver. These process look like

/home/chromedriver --port=12328 --log-path=/var/log/selenium-chrome.log /home/chromedriver --port=20727 --log-path=/var/log/selenium-chrome.log /home/chromedriver --port=28574 --log-path=/var/log/selenium-chrome.log

And so on. Each of them tries to start an instance of chrome at the same time, which in sum leads to a very high load on the server.

The startup script itself looks like this:

 #!/usr/bin/env bash DISPLAY=:1 xvfb-run -a java -jar -Dwebdriver.chrome.driver="/home/chromedriver" -Dwebdriver.chrome.logfile="/var/log/selenium-chrome.log" /home/selenium-server-standalone-3.4.0.jar

Updating the chromedriver and the chrome itself did not lead to anything.

    0