Chromeless: Permission denied

[janschloss]

When running chrome --remote-debugging-port=9222 --disable-gpu --headless this error occurs indefinitely:

[0728/173716.084395:ERROR:crash_report_database_mac.mm(94)] mkdir /Applications/Google Chrome.app/Contents/Versions/60.0.3112.78/Google Chrome Framework.framework/Versions/A/new: Permission denied
[0728/173716.084944:INFO:crashpad_client_mac.cc(295)] restarting handler in 0.987s

[janschloss]

I fixed it by changing the chmod of the "A" folder but should that be necessary?

[timsuchanek]

@janschloss thanks for reporting this! To which chmod did you change the A folder? I had similiar problems with Chrome in the past, using Canary solved these issues. Would using Canary also be an option for you?

[janschloss]

@foreggs Sudo does not work with aliases like displayed in the usage section, however using the the command like sudo /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --disable-gpu --headless works.

@timsuchanek I used sudo chmod a+rwx A inside /Applications/Google Chrome.app/contents/Versions/60.0.3112.78/Google Chrome Framework.framework/Versions. I try to work with the already installed browser if possible.

[junjiemars]

sudo chown -R <user>:<group> A

[jmjpro]

The fix is very temporary as you have to change the directory permissions again once you get a new chrome version. This issue should be reopened.

[kylecordes]

My question here is why Chrome wants to write to a system (non user specific) location, and how it might be possible to persuade it to not do so. (Nor to write anywhere at all, actually.)

[schemacs]

Resolved after adding this --crash-dumps-dir=/tmp/chrome-headless .
Headless permissions