CODEWITHSUNDEEP
seleniumselenium-webdriverselenium-chromedriverapple-m1
em0605
em0605

Reputation: 315

Selenium::WebDriver::Error Chrome Crashed on M1 chip

I've spent several days trying to solve this issue I'm encountering with the following code:

caps = Selenium::WebDriver::Remote::Capabilities.chrome(
      "chromeOptions" => {
        :args => ['--user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36 LegalMonsterNoBlock"']
      }
    )
    driver = Selenium::WebDriver.for :remote, url: selenium_host, :desired_capabilities => caps
    driver.get(url)

I'm trying to run a test that calls this method. The test runs fine. It opens up Chrome runs the test, but whenever I reach the part of my application that calls the above method, the test fails with the following error:

Minitest::UnexpectedError: Selenium::WebDriver::Error::UnknownError: unknown error: Chrome failed to start: crashed
          (chrome not reachable)
          (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
        Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
        System info: host: '7a6aaccda364', ip: '172.17.0.2', os.name: 'Linux', os.arch: 'amd64', os.version: '4.19.121-linuxkit', java.version: '1.8.0_232'
        Driver info: driver.version: unknown
        remote stacktrace: #0 0x0040004b6479 <unknown>

My setup:

I have tried several things already:

Any other experiencing such issues?

Upvotes: 11

Views: 6239

Answers (2)

Arthur Sady Cordeiro Rossetti
Arthur Sady Cordeiro Rossetti

Reputation: 421

For me using a docker image compatible with the arm64 architecture solved the issue. It was easy to set it up after understanding the problem using an image from https://hub.docker.com/u/seleniarm

I just run the command

docker run -d -p 4444:4444 seleniarm/standalone-chromium

This set it up where I needed and worked just fine.

I had the same error when I was trying to run in a docker using the below command.

docker run -d -p 4444:4444 selenium/standalone-chrome

My solution was mentioned in the github answer for the issue posted above and the link to the answer so we can give the proper credits is this:

https://github.com/SeleniumHQ/docker-selenium/issues/1076#issuecomment-788343926

Hope this sheds some light for others.

Upvotes: 4

em0605
em0605

Reputation: 315

It turned out that it is my docker image, that does not support the arm64-architecture, so it was this step: Running a docker selenium/standalone-chrome-debug:3.141.59-zinc.

There was no issue if I disabled the part of the tests that used the docker container. I imagine this is no possible for everyone, but lets hope that there'll be a selenium image that will support arm64 architecture soon.

See Selenium issue here.

Upvotes: 3

Related Questions