What makes this more bizarre, is the cefclient is automatically built with the CEF binary build given the automate-git.py settings and it works fine hitting "chrome://sandbox :
- Code: Select all
$env:CEF_USE_GN=1
$env:GN_ARGUMENTS="--ide=vs2019 --sln=cef --filters=//cef/*"
$env:GN_DEFINES="is_official_build=true proprietary_codecs=true ffmpeg_branding=Chrome use_thin_lto=false"
python3 automate\automate-git.py --download-dir=c:\code\chromium_git --depot-tools-dir=c:\code\depot_tools --branch=4430 --force-clean --force-build --x64-build --no-depot-tools-update
However, if we then take the zipped up CEF binary (cef_binary_90.4.2+gd4386da+chromium-90.0.4430.51_windows64.zip) and kick off the cefclient build using cmake (cmake -G "Visual Studio 16 2019" -A x64) and build the cefclient solution in visual studio, it bombs when hitting that "chrome://sandbox" URL. If I take that cefclient.exe binary produced during the CEF build and drop it in the output folder of this same "crashing" binary it works just fine.