Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[🐛 Bug]: v4.29 Goes into Crash Loop On Startup #2685

Open
twurm opened this issue Feb 27, 2025 · 3 comments
Open

[🐛 Bug]: v4.29 Goes into Crash Loop On Startup #2685

twurm opened this issue Feb 27, 2025 · 3 comments
Labels
needs-triaging

Comments

@twurm
Copy link

twurm commented Feb 27, 2025

What happened?

v4.28.1 works as expected, we upgraded to v.4.29 yesterday and noticed we could no longer connect to the UX. Looking at the logs in Docker we see the following.

2025-02-27 07:20:31 2025-02-27 12:20:31,612 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 07:20:31 #
2025-02-27 07:20:31 # A fatal error has been detected by the Java Runtime Environment:

I do have the hs_err_pid.log if you need it.

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

docker run -d -p 4442-4444:4442-4444 --net grid --name selenium-hub selenium/hub:4.29.0-20250222

Relevant log output

2025-02-27 06:55:51 2025-02-27 11:55:51,966 INFO Included extra file "/etc/supervisor/conf.d/selenium-grid-hub.conf" during parsing
2025-02-27 06:55:51 2025-02-27 11:55:51,968 INFO RPC interface 'supervisor' initialized
2025-02-27 06:55:51 2025-02-27 11:55:51,968 INFO supervisord started with pid 8
2025-02-27 06:55:52 2025-02-27 11:55:52,975 INFO spawned: 'selenium-grid-hub' with pid 9
2025-02-27 06:55:52 Starting Selenium Grid Hub...
2025-02-27 06:55:52 2025-02-27 11:55:52,983 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 06:55:52 Appending Selenium option: --log-level INFO
2025-02-27 06:55:52 Appending Selenium option: --http-logs false
2025-02-27 06:55:52 Appending Selenium option: --structured-logs false
2025-02-27 06:55:52 Appending Selenium option: --reject-unsupported-caps false
2025-02-27 06:55:52 Appending Selenium option: --session-request-timeout 300
2025-02-27 06:55:52 Appending Selenium option: --session-retry-interval 15
2025-02-27 06:55:52 Appending Selenium option: --healthcheck-interval 120
2025-02-27 06:55:52 Appending Selenium option: --relax-checks true
2025-02-27 06:55:52 Appending Selenium option: --bind-host false
2025-02-27 06:55:52 Appending Selenium option: --config /opt/selenium/config.toml
2025-02-27 06:55:52 Appending Selenium option: --tracing false
2025-02-27 06:55:52 Tracing is disabled
2025-02-27 06:55:52 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-27 06:55:53 #
2025-02-27 06:55:53 # A fatal error has been detected by the Java Runtime Environment:
2025-02-27 06:55:53 #
2025-02-27 06:55:53 #  SIGILL (0x4) at pc=0x0000ffff9bd3fc5c, pid=10, tid=11
2025-02-27 06:55:53 #
2025-02-27 06:55:53 # JRE version:  (21.0.6+7) (build )
2025-02-27 06:55:53 # Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-124.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-27 06:55:53 # Problematic frame:
2025-02-27 06:55:53 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-27 06:55:53 #
2025-02-27 06:55:53 # 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-27 06:55:53 #
2025-02-27 06:55:53 # An error report file with more information is saved as:
2025-02-27 06:55:53 # /tmp/hs_err_pid10.log
2025-02-27 06:55:53 [0.023s][warning][os] Loading hsdis library failed
2025-02-27 06:55:53 #
2025-02-27 06:55:53 # The crash happened outside the Java Virtual Machine in native code.
2025-02-27 06:55:53 # See problematic frame for where to report the bug.
2025-02-27 06:55:53 #
2025-02-27 06:55:53 /opt/bin/start-selenium-grid-hub.sh: line 184:    10 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} hub ${SE_OPTS}
2025-02-27 06:55:53 2025-02-27 11:55:53,021 WARN exited: selenium-grid-hub (exit status 134; not expected)
2025-02-27 06:55:54 2025-02-27 11:55:54,024 INFO spawned: 'selenium-grid-hub' with pid 19
2025-02-27 06:55:54 Starting Selenium Grid Hub...
2025-02-27 06:55:54 2025-02-27 11:55:54,028 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 06:55:54 Appending Selenium option: --log-level INFO
2025-02-27 06:55:54 Appending Selenium option: --http-logs false
2025-02-27 06:55:54 Appending Selenium option: --structured-logs false
2025-02-27 06:55:54 Appending Selenium option: --reject-unsupported-caps false
2025-02-27 06:55:54 Appending Selenium option: --session-request-timeout 300
2025-02-27 06:55:54 Appending Selenium option: --session-retry-interval 15
2025-02-27 06:55:54 Appending Selenium option: --healthcheck-interval 120
2025-02-27 06:55:54 Appending Selenium option: --relax-checks true
2025-02-27 06:55:54 Appending Selenium option: --bind-host false
2025-02-27 06:55:54 Appending Selenium option: --config /opt/selenium/config.toml
2025-02-27 06:55:54 Appending Selenium option: --tracing false
2025-02-27 06:55:54 Tracing is disabled
2025-02-27 06:55:54 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-27 06:55:54 #
2025-02-27 06:55:54 # A fatal error has been detected by the Java Runtime Environment:
2025-02-27 06:55:54 #
2025-02-27 06:55:54 #  SIGILL (0x4) at pc=0x0000ffff9fd3fc5c, pid=20, tid=21
2025-02-27 06:55:54 #
2025-02-27 06:55:54 # JRE version:  (21.0.6+7) (build )
2025-02-27 06:55:54 # Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-124.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-27 06:55:54 # Problematic frame:
2025-02-27 06:55:54 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-27 06:55:54 #
2025-02-27 06:55:54 # 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-27 06:55:54 #
2025-02-27 06:55:54 # An error report file with more information is saved as:
2025-02-27 06:55:54 # /tmp/hs_err_pid20.log
2025-02-27 06:55:54 [0.020s][warning][os] Loading hsdis library failed
2025-02-27 06:55:54 #
2025-02-27 06:55:54 # The crash happened outside the Java Virtual Machine in native code.
2025-02-27 06:55:54 # See problematic frame for where to report the bug.
2025-02-27 06:55:54 #
2025-02-27 06:55:54 /opt/bin/start-selenium-grid-hub.sh: line 184:    20 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} hub ${SE_OPTS}
2025-02-27 06:55:54 2025-02-27 11:55:54,060 WARN exited: selenium-grid-hub (exit status 134; not expected)
2025-02-27 06:55:55 2025-02-27 11:55:55,061 INFO spawned: 'selenium-grid-hub' with pid 29
2025-02-27 06:55:55 Starting Selenium Grid Hub...
2025-02-27 06:55:55 2025-02-27 11:55:55,063 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 06:55:55 Appending Selenium option: --log-level INFO
2025-02-27 06:55:55 Appending Selenium option: --http-logs false
2025-02-27 06:55:55 Appending Selenium option: --structured-logs false
2025-02-27 06:55:55 Appending Selenium option: --reject-unsupported-caps false
2025-02-27 06:55:55 Appending Selenium option: --session-request-timeout 300
2025-02-27 06:55:55 Appending Selenium option: --session-retry-interval 15
2025-02-27 06:55:55 Appending Selenium option: --healthcheck-interval 120
2025-02-27 06:55:55 Appending Selenium option: --relax-checks true
2025-02-27 06:55:55 Appending Selenium option: --bind-host false
2025-02-27 06:55:55 Appending Selenium option: --config /opt/selenium/config.toml
2025-02-27 06:55:55 Appending Selenium option: --tracing false
2025-02-27 06:55:55 Tracing is disabled
2025-02-27 06:55:55 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-27 06:55:55 #
2025-02-27 06:55:55 # A fatal error has been detected by the Java Runtime Environment:
2025-02-27 06:55:55 #
2025-02-27 06:55:55 #  SIGILL (0x4) at pc=0x0000ffff9bd3fc5c, pid=30, tid=31
2025-02-27 06:55:55 #
2025-02-27 06:55:55 # JRE version:  (21.0.6+7) (build )
2025-02-27 06:55:55 # Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-124.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-27 06:55:55 # Problematic frame:
2025-02-27 06:55:55 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-27 06:55:55 #
2025-02-27 06:55:55 # 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-27 06:55:55 #
2025-02-27 06:55:55 # An error report file with more information is saved as:
2025-02-27 06:55:55 # /tmp/hs_err_pid30.log
2025-02-27 06:55:55 [0.011s][warning][os] Loading hsdis library failed
2025-02-27 06:55:55 #
2025-02-27 06:55:55 # The crash happened outside the Java Virtual Machine in native code.
2025-02-27 06:55:55 # See problematic frame for where to report the bug.
2025-02-27 06:55:55 #
2025-02-27 06:55:55 /opt/bin/start-selenium-grid-hub.sh: line 184:    30 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} hub ${SE_OPTS}
2025-02-27 06:55:55 2025-02-27 11:55:55,081 WARN exited: selenium-grid-hub (exit status 134; not expected)
2025-02-27 06:55:56 2025-02-27 11:55:56,086 INFO spawned: 'selenium-grid-hub' with pid 39
2025-02-27 06:55:56 Starting Selenium Grid Hub...
2025-02-27 06:55:56 2025-02-27 11:55:56,091 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 06:55:56 Appending Selenium option: --log-level INFO
2025-02-27 06:55:56 Appending Selenium option: --http-logs false
2025-02-27 06:55:56 Appending Selenium option: --structured-logs false
2025-02-27 06:55:56 Appending Selenium option: --reject-unsupported-caps false
2025-02-27 06:55:56 Appending Selenium option: --session-request-timeout 300
2025-02-27 06:55:56 Appending Selenium option: --session-retry-interval 15
2025-02-27 06:55:56 Appending Selenium option: --healthcheck-interval 120
2025-02-27 06:55:56 Appending Selenium option: --relax-checks true
2025-02-27 06:55:56 Appending Selenium option: --bind-host false
2025-02-27 06:55:56 Appending Selenium option: --config /opt/selenium/config.toml
2025-02-27 06:55:56 Appending Selenium option: --tracing false
2025-02-27 06:55:56 Tracing is disabled
2025-02-27 06:55:56 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-27 06:55:56 #
2025-02-27 06:55:56 # A fatal error has been detected by the Java Runtime Environment:
2025-02-27 06:55:56 #
2025-02-27 06:55:56 #  SIGILL (0x4) at pc=0x0000ffff8fd3fc5c, pid=40, tid=41
2025-02-27 06:55:56 #
2025-02-27 06:55:56 # JRE version:  (21.0.6+7) (build )
2025-02-27 06:55:56 # Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-124.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-27 06:55:56 # Problematic frame:
2025-02-27 06:55:56 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-27 06:55:56 #
2025-02-27 06:55:56 # 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-27 06:55:56 #
2025-02-27 06:55:56 # An error report file with more information is saved as:
2025-02-27 06:55:56 # /tmp/hs_err_pid40.log
2025-02-27 06:55:56 [0.020s][warning][os] Loading hsdis library failed
2025-02-27 06:55:56 #
2025-02-27 06:55:56 # The crash happened outside the Java Virtual Machine in native code.
2025-02-27 06:55:56 # See problematic frame for where to report the bug.
2025-02-27 06:55:56 #
2025-02-27 06:55:56 /opt/bin/start-selenium-grid-hub.sh: line 184:    40 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} hub ${SE_OPTS}
2025-02-27 06:55:56 2025-02-27 11:55:56,122 WARN exited: selenium-grid-hub (exit status 134; not expected)
2025-02-27 06:55:57 2025-02-27 11:55:57,134 INFO spawned: 'selenium-grid-hub' with pid 49
2025-02-27 06:55:57 Starting Selenium Grid Hub...
2025-02-27 06:55:57 2025-02-27 11:55:57,140 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 06:55:57 Appending Selenium option: --log-level INFO
2025-02-27 06:55:57 Appending Selenium option: --http-logs false
2025-02-27 06:55:57 Appending Selenium option: --structured-logs false
2025-02-27 06:55:57 Appending Selenium option: --reject-unsupported-caps false
2025-02-27 06:55:57 Appending Selenium option: --session-request-timeout 300
2025-02-27 06:55:57 Appending Selenium option: --session-retry-interval 15
2025-02-27 06:55:57 Appending Selenium option: --healthcheck-interval 120
2025-02-27 06:55:57 Appending Selenium option: --relax-checks true
2025-02-27 06:55:57 Appending Selenium option: --bind-host false
2025-02-27 06:55:57 Appending Selenium option: --config /opt/selenium/config.toml
2025-02-27 06:55:57 Appending Selenium option: --tracing false
2025-02-27 06:55:57 Tracing is disabled
2025-02-27 06:55:57 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-27 06:55:57 #
2025-02-27 06:55:57 # A fatal error has been detected by the Java Runtime Environment:
2025-02-27 06:55:57 #
2025-02-27 06:55:57 #  SIGILL (0x4) at pc=0x0000ffff67d3fc5c, pid=50, tid=51
2025-02-27 06:55:57 #
2025-02-27 06:55:57 # JRE version:  (21.0.6+7) (build )
2025-02-27 06:55:57 # Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-124.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-27 06:55:57 # Problematic frame:
2025-02-27 06:55:57 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-27 06:55:57 #
2025-02-27 06:55:57 # 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-27 06:55:57 #
2025-02-27 06:55:57 # An error report file with more information is saved as:
2025-02-27 06:55:57 # /tmp/hs_err_pid50.log
2025-02-27 06:55:57 [0.019s][warning][os] Loading hsdis library failed
2025-02-27 06:55:57 #
2025-02-27 06:55:57 # The crash happened outside the Java Virtual Machine in native code.
2025-02-27 06:55:57 # See problematic frame for where to report the bug.
2025-02-27 06:55:57 #
2025-02-27 06:55:57 /opt/bin/start-selenium-grid-hub.sh: line 184:    50 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} hub ${SE_OPTS}
2025-02-27 06:55:57 2025-02-27 11:55:57,171 WARN exited: selenium-grid-hub (exit status 134; not expected)
2025-02-27 06:55:58 2025-02-27 11:55:58,175 INFO spawned: 'selenium-grid-hub' with pid 59
2025-02-27 06:55:58 Starting Selenium Grid Hub...
2025-02-27 06:55:58 2025-02-27 11:55:58,178 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 06:55:58 Appending Selenium option: --log-level INFO
2025-02-27 06:55:58 Appending Selenium option: --http-logs false
2025-02-27 06:55:58 Appending Selenium option: --structured-logs false
2025-02-27 06:55:58 Appending Selenium option: --reject-unsupported-caps false
2025-02-27 06:55:58 Appending Selenium option: --session-request-timeout 300
2025-02-27 06:55:58 Appending Selenium option: --session-retry-interval 15
2025-02-27 06:55:58 Appending Selenium option: --healthcheck-interval 120
2025-02-27 06:55:58 Appending Selenium option: --relax-checks true
2025-02-27 06:55:58 Appending Selenium option: --bind-host false
2025-02-27 06:55:58 Appending Selenium option: --config /opt/selenium/config.toml
2025-02-27 06:55:58 Appending Selenium option: --tracing false
2025-02-27 06:55:58 Tracing is disabled
2025-02-27 06:55:58 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-27 06:55:58 #
2025-02-27 06:55:58 # A fatal error has been detected by the Java Runtime Environment:
2025-02-27 06:55:58 #
2025-02-27 06:55:58 #  SIGILL (0x4) at pc=0x0000ffff6bd3fc5c, pid=60, tid=61
2025-02-27 06:55:58 #
2025-02-27 06:55:58 # JRE version:  (21.0.6+7) (build )
2025-02-27 06:55:58 # Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-124.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-27 06:55:58 # Problematic frame:
2025-02-27 06:55:58 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-27 06:55:58 #
2025-02-27 06:55:58 # 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-27 06:55:58 #
2025-02-27 06:55:58 # An error report file with more information is saved as:
2025-02-27 06:55:58 # /tmp/hs_err_pid60.log
2025-02-27 06:55:58 [0.012s][warning][os] Loading hsdis library failed
2025-02-27 06:55:58 #
2025-02-27 06:55:58 # The crash happened outside the Java Virtual Machine in native code.
2025-02-27 06:55:58 # See problematic frame for where to report the bug.
2025-02-27 06:55:58 #
2025-02-27 06:55:58 /opt/bin/start-selenium-grid-hub.sh: line 184:    60 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} hub ${SE_OPTS}
2025-02-27 06:55:58 2025-02-27 11:55:58,199 WARN exited: selenium-grid-hub (exit status 134; not expected)
2025-02-27 06:55:59 2025-02-27 11:55:59,205 INFO spawned: 'selenium-grid-hub' with pid 69
2025-02-27 06:55:59 Starting Selenium Grid Hub...
2025-02-27 06:55:59 2025-02-27 11:55:59,209 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-02-27 06:55:59 Appending Selenium option: --log-level INFO
2025-02-27 06:55:59 Appending Selenium option: --http-logs false
2025-02-27 06:55:59 Appending Selenium option: --structured-logs false
2025-02-27 06:55:59 Appending Selenium option: --reject-unsupported-caps false
2025-02-27 06:55:59 Appending Selenium option: --session-request-timeout 300
2025-02-27 06:55:59 Appending Selenium option: --session-retry-interval 15
2025-02-27 06:55:59 Appending Selenium option: --healthcheck-interval 120
2025-02-27 06:55:59 Appending Selenium option: --relax-checks true
2025-02-27 06:55:59 Appending Selenium option: --bind-host false
2025-02-27 06:55:59 Appending Selenium option: --config /opt/selenium/config.toml
2025-02-27 06:55:59 Appending Selenium option: --tracing false
2025-02-27 06:55:59 Tracing is disabled
2025-02-27 06:55:59 Using JAVA_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/selenium/logs  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-02-27 06:55:59 #
2025-02-27 06:55:59 # A fatal error has been detected by the Java Runtime Environment:
2025-02-27 06:55:59 #
2025-02-27 06:55:59 #  SIGILL (0x4) at pc=0x0000ffff8fd3fc5c, pid=70, tid=71
2025-02-27 06:55:59 #
2025-02-27 06:55:59 # JRE version:  (21.0.6+7) (build )
2025-02-27 06:55:59 # Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-124.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
2025-02-27 06:55:59 # Problematic frame:
2025-02-27 06:55:59 # j  java.lang.System.registerNatives()V+0 [email protected]
2025-02-27 06:55:59 #
2025-02-27 06:55:59 # 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-27 06:55:59 #
2025-02-27 06:55:59 # An error report file with more information is saved as:
2025-02-27 06:55:59 # /tmp/hs_err_pid70.log
2025-02-27 06:55:59 [0.017s][warning][os] Loading hsdis library failed
2025-02-27 06:55:59 #
2025-02-27 06:55:59 # The crash happened outside the Java Virtual Machine in native code.
2025-02-27 06:55:59 # See problematic frame for where to report the bug.
2025-02-27 06:55:59 #
2025-02-27 06:55:59 /opt/bin/start-selenium-grid-hub.sh: line 184:    70 Aborted                 java ${JAVA_OPTS:-$SE_JAVA_OPTS} -jar /opt/selenium/selenium-server.jar ${EXTRA_LIBS} hub ${SE_OPTS}
2025-02-27 06:55:59 2025-02-27 11:55:59,237 WARN exited: selenium-grid-hub (exit status 134; not expected)

Operating System

MacOS 15.3.1 M4

Docker Selenium version (image tag)

4.29.0-20250222

Selenium Grid chart version (chart version)

No response
@twurm
Copy link
Author

twurm commented Feb 27, 2025

I'm attaching the hs_err_pid.log file as well.

hs_err_pid10.log

@github-actions GitHub Actions
Copy link

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

@twurm
Copy link
Author

twurm commented Feb 27, 2025 •
edited
Loading

It seems like the issue is related to: AArch64: VM crashes with SIGILL when prctl is disallowed

To get around this issue you need to create an environment variable _JAVA_OPTIONS=-XX:UseSVE=0 an example is below:

docker run -d -p 4442-4444:4442-4444 --net grid -e _JAVA_OPTIONS=-XX:UseSVE=0 --name selenium-hub selenium/hub:4.29.0-20250222

I'm seeing the same issue with the latest Firefox drivers as well: standalone-firefox, node-firefox the same workaround appears to mitigate the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-triaging
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@twurm