Fail to start cef with VS debugger

[FEssig]

Hi,

We are using cef 3.2704 which is build in a own dll.
When the exe which uses cef is started normal everything works fine.
But if I start the exe using the Visual Studio(2015) debugger cef fails to start.

This is the output in VS:

Code: Select all

[1125/085623:ERROR:main_delegate.cc(724)] Could not load locale pak for de
[1125/085623:ERROR:main_delegate.cc(731)] Could not load cef.pak
[1125/085623:ERROR:main_delegate.cc(748)] Could not load cef_100_percent.pak
[1125/085623:ERROR:main_delegate.cc(757)] Could not load cef_200_percent.pak
[1125/085623:ERROR:main_delegate.cc(766)] Could not load cef_extensions.pak
[1125/085623:ERROR:child_process_launcher.cc(505)] Failed to launch child process
[1125/085623:ERROR:extension_system.cc(72)] Failed to parse extension manifest.
[1125/085623:ERROR:content_client.cc(344)] No data resource available for id 23968
[1125/085623:ERROR:content_client.cc(344)] No data resource available for id 23967
[1125/085624:ERROR:shell.cc(299)] Instance: exe:content_browser attempting to register an instance for a process it created for target: exe:content_renderer without the mojo:shell{client_process} capability class.
[1125/085624:ERROR:child_process_launcher.cc(505)] Failed to launch child process

OS: Windows 8.1 64bit

The problem is we are a bit concerned that the problem is due to the delay during the startup (debugger loading symbols) and thus this could happen if the machine starting the program is slow / under heavy workload.

Any ideas how to solve this problem?

[amaitland]

Error message is usually seen when your missing locals, in your case try setting a fully qualified path to your locales directory.

[FEssig]

Thanks
The debugger actually started the exe from a different location and thus the locales directory couldn't be found.