Comment 20 for bug 1303676

That looks expected. Chromium forks the browser process to use it as a sandbox IPC process, which is great for Chromium (because it forks it at startup and before any threads are created) but sucks for us (because by the time it forks, we already have a QML app and other gunk).

I'm trying to reimplement this at the moment as there's another bug anyway (because threads are never forked, there's a potential deadlock in the child process if fork is called whilst another thread holds a lock in something like malloc)