MacBook Pro M1 - Chromedriver is running the wrong version of chrome (x86_64 instad of arm64)

[jacek cho]

Hi, 

it looks that on my machine MacBook Pro M1 

Chromedriver is running the wrong version of chrome (x86_64 instead of arm64)

which makes the tests run incredibly slow...

This problem occurs both in Java (webdriver manager) and Node.js (Webdriver.io)

chrome installed on my computer:

`Version 114.0.5735.90 (Official Build) (arm64)`

chrome version run by the chromedriver: 

`Version 114.0.5735.90 (Official Build) (x86_64 translated)`

Chromedriver downloaded by webdrivermanager: 

/Users/jchowaniec/.cache/selenium/chromedriver/mac-arm64
jchowaniec@WHM5006400 mac-arm64 % ls
114.0.5735.90

[Mathias Bynens]

This sounds like a problem with the “webdrivermanager” project (downloading and using the wrong Chrome binary), not ChromeDriver itself. Have you reported the issue there?

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/8e2b9de3-de1f-413d-b3c0-63eed7b4eb7dn%40googlegroups.com.

[jacek cho]

Hi,

same problem when downloading and running chromedriver manually
chromedriver: https://chromedriver.storage.googleapis.com/114.0.5735.90/chromedriver_mac_arm64.zip

e.g.
```

System.setProperty("webdriver.chrome.driver", "chromedriver_mac_arm64/chromedriver");
WebDriver driver = new ChromeDriver();
driver.navigate().to("http://google.com");
driver.quit();

```

[die...@gmail.com]

This was indeed a bug in Selenium Manager (which uses the path shown by the user). The bug has been fixed a while ago. If you are using the latest Selenium (4.9.1 at the moment of writing) and you still see this error, please raise an issue at the Selenium project.

[jacek cho]

Hi,

The problem started with chromedriver version 113.  

Both for java (selenium) and for node.js (wdio) 

rolling back the browser version to 110 fixes the issue. 

You received this message because you are subscribed to a topic in the Google Groups "ChromeDriver Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedriver-users/57cdZVRK9xQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/b5ab8013-aa75-43be-846a-bda03915761dn%40googlegroups.com.

[Yoshichika Nagatsuka (Yoshichika)]

Hi,
same here.
I tried to downgraded chrome to 110.0.5481.77 with chrome driver 110.0.5481.77 still have the issue.

2023年6月3日土曜日 0:14:28 UTC+9 jacek cho:

[Jianan Huang]

One possible root cause is: you're using x86_64 version of java/nodejs/python

to exclude this possible root cause, you can manually find the webdriver and start it:

./chromedriver 

Starting ChromeDriver 114.0.5735.90 (386bc09e8f4f2e025eddae123f36f6263096ae49-refs/branch-heads/5735@{#1052}) on port 9515

and then start chrome by http request:

curl -X POST http://localhost:9515/session -d '{"capabilities": {"browserName": "chrome"}}'

if the chrome started by http response is arm64 version, it proves the root cause is in your java/nodejs/python side.

[jacek cho]

Hi,

i finally was able to fix the issue 

the root cause was Intelij / Webstorm.... 
i had to reinstal them to the latests version 
i also updated my java / node version 

[Emre GÜDÜK]

i still can't figure it out, can you help cho?

15 Haziran 2023 Perşembe tarihinde saat 14:49:11 UTC+3 itibarıyla jacek cho şunları yazdı:

[Andy “The Sheriff” Wall]

Also getting this. MacBook Pro M2. I can confirm 64-bit on everything (that I can think of):

• Chromedriver is the latest arm64 Mac build (115.0.5790.102) which matches my Chrome version. 
• The Chrome binary, installed via regular auto-update, includes arm64.
  Note, it does include both:
  • Using file on the binary shows: .../Google Chrome.app/Contents/MacOS/Google Chrome: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable arm64]
  • When run manually, it runs as arm64 (seen in chrome://version)
• The shell is 64-bits (arch returns arm64). 
• Python (where I'm running it from, via selenium.webdriver.Chrome) is also 64-bit, arm64.
  

Yet still, when launched via selenium, chrome://version reports itself as x86_64 translated.

And yeah... it's really slow! Help!

[Артем Крошенинников]

In my case it was a transfer from previous Mac to MacM2 and some processes were still working in `Intel` aka translated mode. It turned out it was Java that was launched in `Intel` mode and thus a Maven/Gradle project that starts the chromedriver was requesting Chrome in this translated mode. Reinstalling brew and Java helped to overcome the problem.

суббота, 22 июля 2023 г. в 07:24:36 UTC+3, Andy “The Sheriff” Wall:

[Renas Aktas]

Has anyone found a solution to this issue yet? I made so many changes but no luck still.

Thanks

[Matt Li]

I just ran into the same situation when running automation tests on Selenium. What I finally figured out is that the version of chrome that Selenium pulls up via chrome driver is dependent on the version of the JVM that you have installed. In my case, I had an x86_64 version of the JDK as my primary project java compiler. Reinstalling my java version, and manually selecting the correct version (and not going through brew) solved this problem.

[西九文化]

Hi all,

Someone in china solved the problem permanently. You can check the link as below: 

https://www.cnblogs.com/kaka0318/p/17650891.html

All the best

Matt Li 在 2023年8月29日 星期二凌晨1:59:23 [UTC+8] 的信中寫道：

[Sergiu Cemirtan]

Updating the node.js version to latests helped me.

[Sibasish Mohanta]

upgrade to latest selenium version. for me its - selenium-4.12.0

delete the selenium folder with sudo permission from - cd /Users/sibasish/.cache/ folder

then its worked for me

[Stephen Di Salvio]

This bug is still happening for some m1/m2 chip mac users on selenium-4.12.0, even after removing the ~/Users/<username>/.cache/selenium folder. The workaround we found was to manually download the correct chromedriver binary version, replace the incorrect 114 chromedriver binary at ~/Users/<username>/.cache/selenium/chromedriver/<mac-x64|mac-arm64>/chromedriver, and then manually update the selenium-manager.json file at ~/Users/<username>/.cache/selenium/selenium-manager.json  to match the manually downloaded chromedriver binary. (also remember to allow the new download to run in your security & privacy settings)

Thanks all for your comments which helped us figure out how to get unblocked on this. Hope this helps someone in the future who runs into this issue.