macOS: Chromium crashes on launch about deno-puppeteer

[LukeChannings]

Good call @pmc-a,

I thought this was something to do with codesign or quarantine, but it turned out to be simpler than that.

Chromium has various helper apps in Chromium.app/Contents/Frameworks/Chromium\ Framework.framework/Versions/<Current Version>/Helpers, each of which need to be marked executable too.

I'm making a PR. In the meantime, you can fix this with:

chmod 755 ~/Library/Caches/deno/deno_puppeteer/chromium/*/chrome-mac/Chromium.app/Contents/Frameworks/Chromium\ Framework.framework/Versions/*/Helpers/*.app/Contents/MacOS/*

[jonasgroendahl]

i get the same

[efraim-andrade]

same here on mac, i try on linux and works normally

[pmc-a]

I was getting the same, but was able to overcome it by specifying the actual path to my Chromium executable path within the puppeteer.launch arguments. Something like this:

const browser = await Puppeteer.launch({
    headless: true,
    executablePath: "/Applications/Chromium.app/Contents/MacOS/Chromium",
});

At a guess, I think this could be because the install cmd actually runs and installs the chromium within the Deno cache and deno-puppeteer is failing to launch it? Not entirely sure.

Hope this helps though!

[felixsanz]

@LukeChannings @lucacasonato

not fixed on linux, just got this on my first usage. what's the fix on linux? permissions seems to not fix it

[caperaven]

I am also getting this issue on windows.
Is there a solution for this yet.