Side Effects of CefInitialize

[illfang]

I'm trying to integrate CEF into an existing framework on linux.
The framework provides a method which will execute a process and return the process exit status.
e.g.

Code: Select all

int exitStatus = Execute(command);

This works fine, however, after calling

Code: Select all

CefInitialize(main_args, settings, app.get(), NULL);

The same function will not return anymore and seems to be stuck trying to retrieve the exit code using waitpid.
The executed process will be marked as a <defunct> zombie process.

Code: Select all

CheckCEFHash(); // works fine, cef library loaded here
int exitStatus = Execute(command); // works fine
CefInitialize(args, settings, application, NULL); // works fine
int exitStatus = Execute(command); // does not return, a defunct zombie process remains


Besides this, everything is working OK so far and I'm able to create browsers using CEF.
I'm wondering what side effects CefInitialize could have which results in the lack of retrieving the exit code of the process afterwards.
Any hint would be greatly appreciated.

[magreenblatt]

How does waitpid work? That might provide a hint.

[illfang]

After debugging the framework more, it seems like waitpid is not getting called because the SIGCHILD handler function is not getting notified anymore after CefInitialize is called.
I guess it makes sense as CEF (I think, more likely Chromium) also wants to track its child processes.
I'm going to try to setup a third handler calling both handlers.

It would be interesting to know which signals are registered during the call.

[magreenblatt]

You can search the Chromium source code here: https://code.google.com/p/chromium/codesearch