[🐛 Bug]: Java Runtime Environment Fatal Error

[softwaresweetsoftware]

What happened?

When running a scraper with selenium grid, I'm receiving a Java Runtime Error ~5-20m into the tests, this Is consistent.

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

# Options       

options = webdriver.FirefoxOptions()
        profile = webdriver.FirefoxProfile()

        # Performance arguments
        options.add_argument("--disable-extensions")
        options.add_argument("--disable-gpu")
        options.add_argument("--no-sandbox")
        options.add_argument("--disable-dev-shm-usage")
        options.add_argument("--disable-setuid-sandbox")
        options.add_argument("--disable-popup-blocking")
        options.add_argument("--disable-infobars")
        options.add_argument("--disable-notifications")
        options.add_argument("--disable-default-apps")
        options.add_argument("--mute-audio")
        options.add_argument("--blink-settings=imagesEnabled=false")

        # Blocks requests to ebay images
        options.set_preference("permissions.default.image", 2)
        options.set_preference("dom.ipc.plugins.enabled.libflashplayer.so", "false")


# Docker Compose File
  selenium:
    image: selenium/standalone-firefox  
    container_name: selenium_chrome
    shm_size: "2gb"
    platform: linux/x86_64
    environment:
      SE_ENABLE_TRACING: false
    networks:
      - scraper_network
    ports:
      - "4444:4444"

Relevant log output

selenium_chrome    | #
selenium_chrome    | # A fatal error has been detected by the Java Runtime Environment:
selenium_chrome    | #
selenium_chrome    | #  SIGSEGV (0xb) at pc=0x00007fffff142d23, pid=55, tid=159
selenium_chrome    | #
selenium_chrome    | # JRE version: OpenJDK Runtime Environment (17.0.12+7) (build 17.0.12+7-Ubuntu-1ubuntu224.04)
selenium_chrome    | # Java VM: OpenJDK 64-Bit Server VM (17.0.12+7-Ubuntu-1ubuntu224.04, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
selenium_chrome    | # Problematic frame:
selenium_chrome    | # V  [libjvm.so+0x747d23]  G1ParScanThreadState::trim_queue_to_threshold(unsigned int)+0x2fb3
selenium_chrome    | #
selenium_chrome    | # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
selenium_chrome    | #
selenium_chrome    | # An error report file with more information is saved as:
selenium_chrome    | # /tmp/hs_err_pid55.log
selenium_chrome    | #
selenium_chrome    | # If you would like to submit a bug report, please visit:
selenium_chrome    | #   https://bugs.launchpad.net/ubuntu/+source/openjdk-17
selenium_chrome    | #
selenium_chrome    | /opt/bin/start-selenium-standalone.sh: line 179:    55 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} ${CHROME_DRIVER_PATH_PROPERTY} ${EDGE_DRIVER_PATH_PROPERTY} ${GECKO_DRIVER_PATH_PROPERTY} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} standalone --session-request-timeout ${SE_SESSION_REQUEST_TIMEOUT} --session-retry-interval ${SE_SESSION_RETRY_INTERVAL} --healthcheck-interval ${SE_HEALTHCHECK_INTERVAL} --relax-checks ${SE_RELAX_CHECKS} --detect-drivers false --bind-host ${SE_BIND_HOST} --config /opt/selenium/config.toml ${SUB_PATH_CONFIG} ${SE_OPTS}
selenium_chrome    | 2024-12-06 19:53:19,617 WARN exited: selenium-standalone (exit status 134; not expected)
selenium_chrome    | 2024-12-06 19:53:19,618 WARN received SIGINT indicating exit request
selenium_chrome    | 2024-12-06 19:53:19,619 INFO waiting for xvfb, vnc, novnc to die
selenium_chrome    | 2024-12-06 19:53:22,624 WARN stopped: novnc (terminated by SIGTERM)
selenium_chrome    | 2024-12-06 19:53:22,625 INFO waiting for xvfb, vnc to die
selenium_chrome    | 2024-12-06 19:53:23,628 WARN stopped: vnc (terminated by SIGTERM)
selenium_chrome    | 2024-12-06 19:53:24,631 WARN stopped: xvfb (terminated by SIGTERM)

Operating System

MacOS

Docker Selenium version (image tag)

latest

Selenium Grid chart version (chart version)

latest

[github-actions]

@hostile-gabriel, 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!

[softwaresweetsoftware]

Please note: This does seem to be a recent change, as running this scraper weeks ago did not seem to have this issue.

[VietND96]

I have no clue on this, however in logs I saw OpenJDK Runtime Environment (17.0.12+7), can you try the latest image, since it is using 17.0.13 - https://github.com/SeleniumHQ/docker-selenium/releases/tag/4.27.0-20241204

[softwaresweetsoftware]

Thanks so much for your response, I haven't tried this fix yet however switching from Firefox to Chrome seems to have eliminated the issue. It arose from a 'Failed to decode response from marionette' leading to a timeout of some kind (propagating as this Java error). however the program was being allocated a generous shm size, memory, and even multiple cores - so it left me pretty stumped. You can close this for now :)

[VietND96]

@hostile-gabriel, if having time, can you try the image tag selenium/standalone-firefox:nightly to see can reproduce or not.
The recent update is Firefox installed via Mozilla APT repo instead of downloading tar.bz2 and extracting it.

[softwaresweetsoftware]

Yes, I will try this when I have the time and report back. Thanks.

[github-actions]

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.