Comment 29 for bug 1300235

Playing around with strings(1), I've found this:

$ strings /usr/lib/chromium-browser/libs/libcontent.so|egrep "\<init\>"
init
The SUID sandbox created a new PID namespace but Zygote is not the init process. Please, make sure the SUID binary is up to date.
Error creating an init process to reap zombies
Failed to init random generator!
Failed to init data channel.
SRTP reset to init state
Failed to init SRTP, err=
Image size must match encoder init configuration size
.init

----------

The key terms here are:

- "Error creating an init process to reap zombies"
- "SUID binary"

See: https://code.google.com/p/chromium/codesearch#chromium/src/content/zygote/zygote_main_linux.cc&sq=package:chromium

It appears chromium creates PID namespaces, probably to run plugins/tabs in an isolated environment. But each pid namespace needs a PID 1 process. So, one possibility is that chromium is inadvertently forking and exec'ing "init" (ie "/sbin/init") rather than its own init implementation of an init daemon ("/opt/google/chrome-unstable/chrome --type=zygote"?). And that init (be it upstart or systemd) is crashing as it's being run in a very unusual environment.