Giters

SeleniumHQ / docker-selenium

Provides a simple way to run Selenium Grid with Chrome, Firefox, and Edge using Container Platform, making it easier to perform browser automation at scale

Home Page:http://www.selenium.dev/docker-selenium/

Repository from Github https://github.comSeleniumHQ/docker-seleniumRepository from Github https://github.comSeleniumHQ/docker-selenium

[🐛 Bug]: A fatal error has been detected by the Java Runtime Environment

KiithNabaal opened this issue · comments

commented

What happened?

I get strange intermittent errors from a Rust server I have deployed on a Microsoft Azure Container App, which connects to a Selenium standalone-chrome container (also on an Azure container app) to do some web automation. Specifically, the Rust server will say it cannot connect to the standalone-chrome container with no indication as to what the problem is. I ran an experiment locally to see if I can reproduce the issue, and while viewing the container's run output in Docker Desktop it reported (truncated, see logs below):

2025-02-05 16:52:31 #
2025-02-05 16:52:31 # A fatal error has been detected by the Java Runtime Environment:
2025-02-05 16:52:31 #
2025-02-05 16:52:31 # SIGSEGV (0xb) at pc=0x00007ffffe936333, pid=58, tid=154

which terminated the Selenium connection I had. I didn't do anything other than try to establish a connection and it immediately crashed. This doesn't happen all of the time; only seemingly randomly... but it does feel like this happens on a first run, and is a bit smoother afterwards. So ex: it crashes, I restart the container and try to connect again, and then it works.

I also checked the logs for the container running Selenium standalone-chrome, but don't see the same output as above, although I am not sure if that would be caught by Azure? My laptop has significantly more resources than what we allocate to any Azure container.

I understand the error may not be fixable by Selenium devs, but was hoping maybe other people have seen this or any pointers on how to proceed?

Any help is appreciated.

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

docker pull --platform linux/x86_64 selenium/standalone-chrome:131.0

Then opened up Docker Desktop and:
Images > click on selenium/standalone-chrome > run > mapped port 4444:4444 (so I could view the dashboard) and container name to "chromedriver"

Relevant log output

2025-02-05 16:21:46 display-name = "chrome"
2025-02-05 16:21:46 stereotype = '{"browserName": "chrome", "browserVersion": "132.0", "platformName": "Linux", "goog:chromeOptions": {"binary": "/usr/bin/google-chrome"}, "se:containerName": "18d8878d37e8", "container:hostname": "18d8878d37e8"}'
2025-02-05 16:21:46 max-sessions = 1
2025-02-05 16:21:46 
2025-02-05 16:21:46 Starting Selenium Grid Standalone...
2025-02-05 16:21:46 Appending Selenium option: --tracing false
2025-02-05 16:21:46 Tracing is disabled
2025-02-05 16:21:46 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.log.LoggingOptions getTracer
2025-02-05 16:21:47 INFO: Using null tracer
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.log.LoggingOptions getTracer
2025-02-05 16:21:47 INFO: Using null tracer
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.node.config.NodeOptions getSessionFactories
2025-02-05 16:21:47 INFO: Detected 12 available processors
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.node.config.NodeOptions report
2025-02-05 16:21:47 INFO: Adding chrome for {"browserName": "chrome","browserVersion": "132.0","container:hostname": "18d8878d37e8","goog:chromeOptions": {"binary": "\u002fusr\u002fbin\u002fgoogle-chrome"},"platformName": "linux","se:containerName": "18d8878d37e8","se:noVncPort": 7900,"se:vncEnabled": true} 1 times
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.node.Node <init>
2025-02-05 16:21:47 INFO: Binding additional locator mechanisms: relative
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.distributor.GridModel setAvailability
2025-02-05 16:21:47 INFO: Switching Node cde4e502-5a65-475e-b970-2750496d8626 (uri: http://172.17.0.2:4444) from DOWN to UP
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.distributor.local.LocalDistributor add
2025-02-05 16:21:47 INFO: Added node cde4e502-5a65-475e-b970-2750496d8626 at http://172.17.0.2:4444. Health check every 120s
2025-02-05 16:21:47 Feb 05, 2025 9:21:47 PM org.openqa.selenium.grid.commands.Standalone execute
2025-02-05 16:21:47 INFO: Started Selenium Standalone 4.28.1 (revision 73f5ad48a2): http://172.17.0.2:4444
2025-02-05 16:26:15 #
2025-02-05 16:26:15 # A fatal error has been detected by the Java Runtime Environment:
2025-02-05 16:26:15 #
2025-02-05 16:26:15 #  SIGSEGV (0xb) at pc=0x00007ffffe938370, pid=58, tid=142
2025-02-05 16:26:15 #
2025-02-05 16:26:15 # JRE version: OpenJDK Runtime Environment (17.0.13+11) (build 17.0.13+11-Ubuntu-2ubuntu124.04)
2025-02-05 16:26:15 # Java VM: OpenJDK 64-Bit Server VM (17.0.13+11-Ubuntu-2ubuntu124.04, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
2025-02-05 16:26:15 # Problematic frame:
2025-02-05 16:26:15 # V  [libjvm.so+0x748370]  G1ParScanThreadState::steal_and_trim_queue(GenericTaskQueueSet<OverflowTaskQueue<ScannerTask, (MEMFLAGS)5, 131072u>, (MEMFLAGS)5>*)+0x1e0
2025-02-05 16:26:15 #
2025-02-05 16:26:15 # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
2025-02-05 16:26:15 #
2025-02-05 16:26:15 # An error report file with more information is saved as:
2025-02-05 16:26:15 # /tmp/hs_err_pid58.log
2025-02-05

Operating System

macOS Sonoma 14.4

Docker Selenium version (image tag)

131.0

Selenium Grid chart version (chart version)

No response

commented

@KiithNabaal, 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!

commented

Can you have a try with this image selenium/standalone-chrome:nightly?

commented

This is looking pretty good so far. Ran my test like eight times, including multiple container restarts and so far it has been running well! I will be hopping off in a moment, but next I will upload this to Azure and run a few more tests.

Thanks!

commented

A difference in that image is using JDK21 instead of JDK17 in the released image. I think you can use this image temporary for a while before the next deployment.

commented

So I was able to run nightly on Azure and sadly this doesn't seem to have resolved my connection issues. I was able to look at the log stream and it seems that I am getting a WebDriverException. Since that is a separate problem, I will create a separate ticket. Thanks again!

commented

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.