Resolving Chromium Issue: Job failed to exec(3) for weird reason: 13

From Chromium build 192300, will not start, throwing a few particular Console errors. These are related to a few key files not coming executable. Read on for instructions on how to fix this.

By Matthew Malinowski, 2013-04-15

I use Chromium nightly builds. Chromium has all the benefits of Chrome, without the extra Google stuff. It's harder to get Chromium going, but once you get the routine down it's pretty smooth.

For the last few builds -- from roughly 192300 -- I've had a problem getting the OS X Chromium nightlies to start.

Console says:

2013/4/15 9:09:23.610 AM[232]: ([0x0-0x3b03b].org.chromium.Chromium[645]) Job failed to exec(3) for weird reason: 13
2013/4/15 9:09:23.611 AM Dock[252]: no information back from LS about running process

The operative phrase there is "Job failed to exec(3) for weird reason: 13". Error type 13 is a permissions error. In this case, I discovered that this means the script inside the Chromium app package isn't executable. (For some reason, OS X pretty regularly makes my stuff executable that shouldn't be, like .gitignore, and vice versa.)

Revised 2013-04-17 to include full list of files:

There are a bunch of scripts inside the Chromium app package that need to be made executable with chmod +x to resolve this issue.

As of 192542, here's (what I think is) the full list:

/path/to/\ Framework.framework/Chromium\ Framework
/path/to/\ Framework.framework/Internet\ Plug-Ins/nacl_irt_x86_32.nexe
/path/to/\ Framework.framework/Libraries/
/path/to/\ Framework.framework/Resources/
/path/to/\ Framework.framework/Resources/crash_inspector
/path/to/\ Helper\\ Helper\ EH
/path/to/\ Helper\\ Helper\ NP
/path/to/\\ Helper

If Chromium is unstable or seems to hang, it's possible you missed one of these. You may see an error like this in Console:

LaunchProcess: failed to execvp:
/Applications/ Helper

Or, you may not.

Back to Blog Index...