Open cseagul opened 1 month ago
interesting - it works on wallaby, "~> 0.29.0"
something happened on wallaby, "~> 0.30"
that is breaking it
I encounter this same issue, thanks for sharing the 0.29 hint. On MacOS the latest 0.30 works flawlessly with Chrome. However, on Ubuntu I get random "invalid session id" errors. It's difficult to debug. When using a single Chromedriver session, the errors are random but when using more than one session, the runtime errors become systematic. On MacOS I can run multiple sessions simultaneously.
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, driver: Wallaby.Chrome, hackney_options: [timeout: :infinity, recv_timeout: :infinity, pool: :wallaby_pool], chromedriver: [ binary: "/opt/chrome/chrome-linux64/chrome", path: "/opt/chromedriver/chromedriver-linux64/chromedriver", capabilities: %{ chromeOptions: %{ args: [ "--headless", "--no-sandbox", "window-size=1600,900", "--fullscreen", "--disable-gpu", "--disable-dev-shm-usage" ] } } ]
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