Enabled Sandbox Segfault Determining it's Functioning - 4430

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby leeroy » Fri Apr 09, 2021 3:03 pm

Based on linker input for this project it IS linking the cef_sandbox lib (..\lib\cef\Debug\cef_sandbox.lib;)

Yes, this app follows a similar pattern to that of the cefclient sample, I'll do a more thorough walk through to be sure anything sandbox doesn't differ and report back.
leeroy
Techie
 
Posts: 47
Joined: Mon Jan 06, 2020 6:27 pm

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby leeroy » Fri Apr 09, 2021 6:29 pm

I rewrote some of this to just use your cefclient's cefclient_win and same issue. I'm starting to think there is something misconfigured in our cmake config, maybe a path change, but I wouldn't understand how this would even build.
leeroy
Techie
 
Posts: 47
Joined: Mon Jan 06, 2020 6:27 pm

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby leeroy » Tue Apr 13, 2021 2:29 pm

@magreenblatt I whittled our app down to a nub, then figured I should try building your "cefclient" directly using the same settings and sure enough it fails in the same way.

OS: Windows Server 2016 Datacenter
Version: 1607
OS Build 14393.2972

CEF: cef_binary_90.4.2+gd4386da+chromium-90.0.4430.51_windows64

CMAKE
Code: Select all
PS C:\basedir\cef> cmake -G "Visual Studio 16 2019" -A x64
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.


-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.14393.
-- The C compiler identification is MSVC 19.28.29913.0
-- The CXX compiler identification is MSVC 19.28.29913.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning (dev) at CMakeLists.txt:207 (find_package):
  Policy CMP0074 is not set: find_package uses <PackageName>_ROOT variables.
  Run "cmake --help-policy CMP0074" for policy details.  Use the cmake_policy
  command to set the policy and suppress this warning.

  CMake variable CEF_ROOT is set to:

    C:/basedir/cef

  For compatibility, CMake is ignoring the variable.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- *** CEF CONFIGURATION SETTINGS ***
-- Generator:                    Visual Studio 16 2019
-- Platform:                     Windows
-- Project architecture:         x86_64
-- Binary distribution root:     C:/basedir/cef
-- Visual Studio ATL support:    ON
-- CEF sandbox:                  ON
-- Standard libraries:           comctl32.lib;rpcrt4.lib;shlwapi.lib;ws2_32.lib;Advapi32.lib;dbghelp.lib;Delayimp.lib;OleAut32.lib;PowrProf.lib;Propsys.lib;psapi.lib;SetupAPI.lib;Shell32.lib;version.lib;wbemuuid.lib;winmm.lib
-- Compile defines:              __STDC_CONSTANT_MACROS;__STDC_FORMAT_MACROS;WIN32;_WIN32;_WINDOWS;UNICODE;_UNICODE;WINVER=0x0601;_WIN32_WINNT=0x601;NOMINMAX;WIN32_LEAN_AND_MEAN;_HAS_EXCEPTIONS=0;PSAPI_VERSION=1;CEF_USE_SANDBOX;CEF_USE_ATL
-- Compile defines (Debug):
-- Compile defines (Release):    NDEBUG;_NDEBUG
-- C compile flags:              /MP;/Gy;/GR-;/W4;/WX;/wd4100;/wd4127;/wd4244;/wd4481;/wd4512;/wd4701;/wd4702;/wd4996;/Zi
-- C compile flags (Debug):      /MTd;/RTC1;/Od
-- C compile flags (Release):    /MT;/O2;/Ob2;/GF
-- C++ compile flags:            /MP;/Gy;/GR-;/W4;/WX;/wd4100;/wd4127;/wd4244;/wd4481;/wd4512;/wd4701;/wd4702;/wd4996;/Zi
-- C++ compile flags (Debug):    /MTd;/RTC1;/Od
-- C++ compile flags (Release):  /MT;/O2;/Ob2;/GF
-- Exe link flags:                /MANIFEST:NO;/LARGEADDRESSAWARE
-- Exe link flags (Debug):       /DEBUG
-- Exe link flags (Release):
-- Shared link flags:
-- Shared link flags (Debug):    /DEBUG
-- Shared link flags (Release):
-- CEF Binary files:             chrome_elf.dll;libcef.dll;libEGL.dll;libGLESv2.dll;snapshot_blob.bin;v8_context_snapshot.bin;swiftshader;d3dcompiler_47.dll
-- CEF Resource files:           chrome_100_percent.pak;chrome_200_percent.pak;resources.pak;icudtl.dat;locales
-- Configuring done
-- Generating done
-- Build files have been written to: C:/basedir/cef


Additional Dependencies:
Code: Select all
..\..\Debug\libcef.lib;..\..\libcef_dll_wrapper\Debug\libcef_dll_wrapper.lib;comctl32.lib;rpcrt4.lib;shlwapi.lib;ws2_32.lib;d3d11.lib;glu32.lib;imm32.lib;opengl32.lib;oleacc.lib;..\..\Debug\cef_sandbox.lib;Advapi32.lib;dbghelp.lib;Delayimp.lib;OleAut32.lib;PowrProf.lib;Propsys.lib;psapi.lib;SetupAPI.lib;Shell32.lib;version.lib;wbemuuid.lib;winmm.lib;kernel32.lib;user32.lib;gdi32.lib;winspool.lib;shell32.lib;ole32.lib;oleaut32.lib;uuid.lib;comdlg32.lib;advapi32.lib
leeroy
Techie
 
Posts: 47
Joined: Mon Jan 06, 2020 6:27 pm

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby magreenblatt » Tue Apr 13, 2021 2:50 pm

What settings did you change?
magreenblatt
Site Admin
 
Posts: 10848
Joined: Fri May 29, 2009 6:57 pm

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby leeroy » Tue Apr 13, 2021 3:04 pm

By settings I mean the cmake settings, "cmake -G "Visual Studio 16 2019" -A x64"

Also using cmake version 3.20.0.
leeroy
Techie
 
Posts: 47
Joined: Mon Jan 06, 2020 6:27 pm

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby leeroy » Tue Apr 13, 2021 4:03 pm

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.
leeroy
Techie
 
Posts: 47
Joined: Mon Jan 06, 2020 6:27 pm

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby magreenblatt » Tue Apr 13, 2021 4:31 pm

I'm able to reproduce the problem and have filed https://bitbucket.org/chromiumembedded/cef/issues/3109
magreenblatt
Site Admin
 
Posts: 10848
Joined: Fri May 29, 2009 6:57 pm

Re: Enabled Sandbox Segfault Determining it's Functioning -

Postby leeroy » Tue Apr 13, 2021 5:28 pm

Perfect, thanks again magreenblatt! We'll track there as well.
leeroy
Techie
 
Posts: 47
Joined: Mon Jan 06, 2020 6:27 pm

Previous

Return to Support Forum

Who is online

Users browsing this forum: Google [Bot] and 27 guests