-
-
Notifications
You must be signed in to change notification settings - Fork 198
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.
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
ChromeDriver failing with invalid session id #787
Comments
interesting - it works on |
I encounter this same issue, thanks for sharing the 0.29 hint. |
I resolved this issue with the latest 0.30.9 Wallaby version on Linux by disabling SHM in the Chrome options. It depends on your environment but by default this can be a very small /dev/shm folder of shared memory and Chrome can run out, causing Wallaby to fail with an "invalid session id" error. By disabling it, it will use /tmp which has more space by default. Obviously an alternative is to grow SHM. config :wallaby, |
Hi
I am trying to set up wallaby on my new linux computer but keep getting
** (RuntimeError) invalid session id
every time I try to visit any site.In the past I have always gotten this error when ChromeDriver and Chrome versions did not match - but now the versions are the same
Environment:
Ubuntu 24.04 LTS
Erlang/OTP 25
Elixir (1.14.0)
wallaby, "~> 0.30"
ChromeDriver 127.0.6533.88
Google Chrome 127.0.6533.99
Here is the session:
When I try to go to the session_url manually I get the following error (even while the Wallaby test is still running)
Any help would be appreciated
Thank you very much
The text was updated successfully, but these errors were encountered: