[Bug]: playwright is launching the chrome x86_64 version on the Mac book M3

[jagadish1010]

Version

v1.49.1

Steps to reproduce

1. Install the chrome on Mac M3
2. file "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
   /Applications/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]
   /Applications/Google Chrome.app/Contents/MacOS/Google Chrome (for architecture x86_64): Mach-O 64-bit executable x86_64
   /Applications/Google Chrome.app/Contents/MacOS/Google Chrome (for architecture arm64): Mach-O 64-bit executable arm64

It has binary with 2 architectures.
3. When we launch the browser using playwright it is picking the intel chip chrome instead of the Mach-O 64-bit executable arm64.
4. Using the java code to launch
5. Sample code :
6. case "chrome":
browserType = playwright.chromium();
launchOptions.setChannel("chrome");
break;

Expected behavior

Expected to launch the browser with architecture arm64

Actual behavior

Launching the browser with architecture x86_64

Additional context

No response

Environment

Mac Book Pro 3
Chip : Apple M3 chip pro

[mxschmitt]

Could you try if the steps in #23914 (comment) help? Looks similar to #23914

[jagadish1010]

@mxschmitt : I tried these steps

Rosetta emulated is not enabled.

Emulate using Rosetta I don't see this option in the chrome.

[mxschmitt]

What's the output of file $(which java)?

[jagadish1010]

/Users/jhatti/.sdkman/candidates/java/current/bin/java: Mach-O 64-bit executable arm64

[dgozman]

@jagadish1010 Unfortunately, the problem is most likely in your setup. Even if you share a repro, running it on our hardware probably won't reproduce the issue. Try looking around for the executable properties of your java, node that is bundled with Playwright and/or any settings. How do you know that Playwright is launching the x86_64 version of the browser? Share any insights here, and try your luck at our Discord server.

[jagadish1010]

@dgozman : When I see the version of the browser launched using the playwright

Browser version launched with Playwright

Browser version in normal :

[Skn0tt]

This is most definitely something specific to your setup, so i'll go ahead and mark it closed for housekeeping purposes. Feel free to continue sharing your findings here, it might help others with the same problem! As Dmitry noted, try looking at the executable properties of java and node. If one of them is started in x86 compatibility mode, there's a good chance that that also influences what mode Chrome is started in.