Both project have access to the same DLLs, pak files, etc...
There are two main differences between the demo project and the existing project:
The number of processes spawned after CefInitialize and the fact that OnBrowserCreated is not called after CreateBrowser.
Some more details about these problems below.
1) Behavior after CefInitialize:
Demo project:
3 processes are spawned:
"--type=gpu-process"
"--type=utility --service-sandbox-type=network"
"--type=utility --service-sandbox-type=utility"
Existing project:
only 1 process is spawned:
"--type=gpu-process"
2) Behavior after CefBrowserHost::CreateBrowser
Demo project:
Callback OnBrowserCreated is called and two renderer processes are spawned.
Existing project:
Callback OnBrowserCreated is never called! No renderer process is spawned.
Debug.log:
A run in debug mode results in the following logging in both projects:
- Code: Select all
[0106/113656.537:INFO:content_main_runner_impl.cc(960)] Chrome is running in full browser mode.
[0106/113656.762:WARNING:angle_platform_impl.cc(52)] initializeD3DDevice(721): Failed creating Debug D3D11 device - falling back to release runtime.
About CefInitialize
Both projects spawn the same executable "CefSubProcess".
- Code: Select all
CefString(&settings.browser_subprocess_path).FromASCII("CefSubProcess.exe");
settings.multi_threaded_message_loop = false;
settings.no_sandbox = true;
Any idea what might trigger the different behavior between both programs sharing the same CEF code? I use Chromium 78.3.9.
Thank you!