Firefox container exiting when running locally

[Jared Lockhart]

We use the Firefox container locally to run integration tests with VNC, however it appears to be exiting abnormally:

firefox-1  | Starting Selenium Grid Standalone...
firefox-1  | Tracing is disabled
firefox-1  | 21:17:31.633 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
firefox-1  | 21:17:31.671 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
firefox-1  | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
firefox-1  | /opt/bin/start-selenium-standalone.sh: line 123:   109 Segmentation fault      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} --bind-host ${SE_BIND_HOST} --config /opt/selenium/config.toml ${SUB_PATH_CONFIG} ${SE_OPTS}
firefox-1  | 2024-03-07 21:17:37,962 INFO exited: selenium-standalone (exit status 139; not expected)
firefox-1  | 2024-03-07 21:17:37,963 WARN received SIGINT indicating exit request
firefox-1  | 2024-03-07 21:17:37,963 INFO waiting for xvfb, vnc, novnc to die
firefox-1  | 2024-03-07 21:17:39,192 INFO stopped: novnc (terminated by SIGTERM)
firefox-1  | 2024-03-07 21:17:39,293 INFO stopped: vnc (terminated by SIGTERM)
firefox-1  | 2024-03-07 21:17:40,295 INFO stopped: xvfb (terminated by SIGTERM)
firefox-1 exited with code 0

Let's figure out why and try to get it functioning again.

┆Issue is synchronized with this Jira Task

[Jared Lockhart]

This has now been fixed by rolling back to a previous version of the selenium-grid container.