cef 3626 (chromium update to 72) build is failing in windows

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.

cef 3626 (chromium update to 72) build is failing in windows

Postby Satrajit » Wed Feb 20, 2019 6:04 am

06:12:15 [33939/34587] ACTION //v8:run_mksnapshot_default(//build/toolchain/win:win_clang_x64)
06:12:15 FAILED: gen/v8/embedded.S snapshot_blob.bin
06:12:15 C:/u/workspace/dev/chromiumwinVir/3626/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../v8/tools/run.py ./mksnapshot --turbo_instruction_scheduling --embedded_src gen/v8/embedded.S --embedded_variant Default --random-seed 314159265 --startup_blob snapshot_blob.bin
06:12:15 ninja: build stopped: subcommand failed.

The build is failing in v8/embedded.S snapshot_blob.bin

have anyone faced this issue?
Satrajit
Mentor
 
Posts: 87
Joined: Wed Jan 09, 2019 6:11 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby ndesktop » Wed Feb 20, 2019 7:29 am

These few lines do not show a helpful error message. I just built 3.3626.1875.g0f098ac on Windows 7 x64.
Looks like an interrupted/incomplete checkout to me.
ndesktop
Master
 
Posts: 756
Joined: Thu Dec 03, 2015 10:10 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby Satrajit » Wed Feb 20, 2019 11:11 am

I was building 3.3626.1886.g162fdec
This is actually failing in my windows machine everytime I am trying
Satrajit
Mentor
 
Posts: 87
Joined: Wed Jan 09, 2019 6:11 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby ndesktop » Wed Feb 20, 2019 1:06 pm

Recheck all the requirements, try to rerun with automate-git.py --no-update --no-cef-update --force-build.
Other than that, try a clean build into a short-length directory, i.e. C:\cef, not C:\Users\user\Desktop\My Downloaded CEF.
I saw failures on Win7 when the path is too long.
ndesktop
Master
 
Posts: 756
Joined: Thu Dec 03, 2015 10:10 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby HarmlessDave » Wed Feb 20, 2019 2:05 pm

You should also have 16 GB of RAM and more than 85 GB of disk space since the cef folder requires 81+ GB
HarmlessDave
Expert
 
Posts: 370
Joined: Fri Jul 11, 2014 2:02 pm

Re: cef 3626 (chromium update to 72) build is failing in win

Postby Egle » Thu Dec 03, 2020 4:18 pm

Hi,
I have looked at the requirements and they are accurate
Windows Configuration What's Required for branch 3770 --> (refs/tags/75.0.3770.100)
Win 7+, VS2017 15.7.1+, Win 10.0.17763 SDK, Ninja
I have Windows10, VS 2017 v 15.9.28, Win 10.0.17763 SDK e Ninja.
I regressed the version of Windows SDK to the one indicated because the v10.0.19041.1 actually gave problems.
The path is simply C:\code\chromium_git3770\chromium\src as you can see from the log.
I just want to recompile the Cef of this specific version with support for mp4 files, but in the Windows environment so far it has been a tragedy, and I had to get by on my own.
Last error encountered:
C:\code\chromium_git3770\chromium\src>ninja -C out\Debug_GN_x86 cef
ninja: Entering directory `out\Debug_GN_x86'
[1/1] Regenerating ninja files
[20266/36949] ACTION //cef:make_pack_header_resources(//build/toolchain/win:win_clang_x86)
File includes/include/cef_pack_resources.h updated.
[20268/36949] ACTION //cef:make_pack_header_strings(//build/toolchain/win:win_clang_x86)
File includes/include/cef_pack_strings.h updated.
[30545/36949] ACTION //tools/v8_context_snapshot:gener..._context_snapshot(//build/toolchain/win:win_clang_x86)
FAILED: v8_context_snapshot.bin
C:/code/depot_tools/bootstrap-3_8_0_chromium_8_bin/python/bin/python.exe ../../build/gn_run_binary.py ./v8_context_snapshot_generator --output_file=v8_context_snapshot.bin
[1203/185351.657:FATAL:com_init_check_hook.cc(159)] Check failed: false. CoCreateInstance appears to be previously patched. <cc cc cc cc cc e9 2b> Attempted to write <e9 80 2f d6 91 eb f9>
Backtrace:
base::debug::CollectStackTrace [0x0836CDEC+60] (C:\code\chromium_git3770\chromium\src\base\debug\stack_trace_win.cc:284)
base::debug::StackTrace::StackTrace [0x06ADC01E+78] (C:\code\chromium_git3770\chromium\src\base\debug\stack_trace.cc:206)
base::debug::StackTrace::StackTrace [0x06ADBF92+34] (C:\code\chromium_git3770\chromium\src\base\debug\stack_trace.cc:203)
logging::LogMessage::~LogMessage [0x05961A84+148] (C:\code\chromium_git3770\chromium\src\base\logging.cc:589)
base::win::`anonymous namespace'::HookManager::WriteHook [0x08398B40+880] (C:\code\chromium_git3770\chromium\src\base\win\com_init_check_hook.cc:166)
base::win::`anonymous namespace'::HookManager::RegisterHook [0x083985CF+63] (C:\code\chromium_git3770\chromium\src\base\win\com_init_check_hook.cc:99)
base::win::ComInitCheckHook::ComInitCheckHook [0x083984DB+27] (C:\code\chromium_git3770\chromium\src\base\win\com_init_check_hook.cc:314)
base::internal::ThreadPoolImpl::ThreadPoolImpl [0x06B47156+758] (C:\code\chromium_git3770\chromium\src\base\task\thread_pool\thread_pool_impl.cc:68)
base::internal::ThreadPoolImpl::ThreadPoolImpl [0x06B46D95+101] (C:\code\chromium_git3770\chromium\src\base\task\thread_pool\thread_pool_impl.cc:56)
std::__1::make_unique<base::internal::ThreadPoolImpl,base::BasicStringPiece<std::__1::basic_string<char> > &> [0x05A2E735+101] (C:\code\chromium_git3770\chromium\src\buildtools\third_party\libc++\trunk\include\memory:3131)
base::ThreadPool::Create [0x05A2E4BD+61] (C:\code\chromium_git3770\chromium\src\base\task\thread_pool\thread_pool.cc:74)
base::ThreadPool::CreateAndStartWithDefaultParams [0x05A2E45B+59] (C:\code\chromium_git3770\chromium\src\base\task\thread_pool\thread_pool.cc:50)
main [0x011D10B0+176] (C:\code\chromium_git3770\chromium\src\tools\v8_context_snapshot\v8_context_snapshot_generator.cc:46)
invoke_main [0x0C6F43EE+30] (d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78)
__scrt_common_main_seh [0x0C6F4557+343] (d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
__scrt_common_main [0x0C6F462D+13] (d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:331)
mainCRTStartup [0x0C6F4638+8] (d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_main.cpp:17)
BaseThreadInitThunk [0x769E8494+36]
RtlAreBitsSet [0x77014328+136]
RtlAreBitsSet [0x770142F8+88]

./v8_context_snapshot_generator failed with exit code 0x80000003
[30558/36949] CXX obj/components/download/public/common/interfaces/download_stream.mojom.obj
ninja: build stopped: subcommand failed.

What is the point of making a forum available and not clarifying errors.
Best regards
Egle
Egle
Newbie
 
Posts: 6
Joined: Thu Nov 26, 2020 6:12 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby ndesktop » Fri Dec 04, 2020 1:48 am

Maybe you are not using the automate-git.py available at the time when 3626 was released?
There are known cases when an automate-git.py newer than the branch breaks.
ndesktop
Master
 
Posts: 756
Joined: Thu Dec 03, 2015 10:10 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby Egle » Fri Dec 04, 2020 8:32 am

Hi
Thanks for the answer first of all.
I tried, because the automate-git.py I am using is the suggested and downloaded from https://bitbucket.org/chromiumembedded/ ... QuickStart.
I also wanted to download the master later If I can.
Now I've rebuild and redid the whole process (update.bat, create.bat e Ninja buil) with his original branch file, but I got the same error; see error and stack below.
The only difference is that it took a lot less time to compile
I have seen that some problems with v8_context_snapshot.bin someone has already had them, but I don't understand if there is a solution.
https://bugs.chromium.org/p/chromium/is ... ?id=764327
where suggested running "gn clean" before a full build resolves the issue???
Thanks a lot
Best regards
Egle


C:\code\chromium_git3770\chromium\src>ninja -C out\Debug_GN_x86 cef
ninja: Entering directory `out\Debug_GN_x86'
[1/1] Regenerating ninja files
[5662/6393] ACTION //tools/v8_context_snapshot:gen...text_snapshot(//build/toolchain/win:win_clang_x86)
FAILED: v8_context_snapshot.bin
C:/code/depot_tools/bootstrap-3_8_0_chromium_8_bin/python/bin/python.exe ../../build/gn_run_binary.py ./v8_context_snapshot_generator --output_file=v8_context_snapshot.bin
[1204/132203.765:FATAL:com_init_check_hook.cc(159)] Check failed: false. CoCreateInstance appears to be previously patched. <cc cc cc cc cc e9 2b> Attempted to write <e9 80 2f d2 91 eb f9>
.......
./v8_context_snapshot_generator failed with exit code 0x80000003
[5675/6393] CXX obj/ui/web_dialogs/web_dialogs/web_dialog_web_contents_delegate.obj
ninja: build stopped: subcommand failed.
Egle
Newbie
 
Posts: 6
Joined: Thu Nov 26, 2020 6:12 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby ndesktop » Fri Dec 04, 2020 9:34 am

First make absolutely sure there is no 3rd party interceptor, AV etc. software.
Then - if you rerun ninja, it will fail in the same place?
ndesktop
Master
 
Posts: 756
Joined: Thu Dec 03, 2015 10:10 am

Re: cef 3626 (chromium update to 72) build is failing in win

Postby Egle » Fri Dec 04, 2020 11:32 am

Hi
Sorry, I didn't understand what you mean by "First make absolutely sure there is no 3rd party interceptor, AV etc. software".
In C:\code\..... path there is only the downloaded material needed for this build.
Then " if you rerun ninja, it will fail in the same place?" Yes, it is.
Now i just did gn clean on all out paths and I am redoing the process, but it will take at least another 4 hours to compile. I'll let you know again later. Thanks

P.S: I also wanted to inform you that the instructions suggested in QuickStart, ok are precious and useful to understand the process, but very incomplete as regards the drawing on a windows environment.
Since until now I have had to fight on everything, I would appreciate, so I have already prepared it if you want, a mini guide for us nerdy .Net followers.
How to resolve Errors:
First error on DEPOT_TOOLS_WIN_TOOLCHAIN , necessary to set environment variable to 0.
Second error on gclient runhooks , fails--> retry running “gclient runhooks” from the chromium/src directory , the first time it fails always.
Third error on depot_tools need to install winapi too! With C:\code\depot_tools>python -m pip install pywin32
Fourth Error on SDK tool .The SDK's module.h passes a lambda to an function that requires a specific calling function and there is no way to specify calling conventions in a lambda. This works in VC++ due to it implementing _all_ calling functions but it fails in 32-bit clang-cl builds. Revert istalled SDK tool to previus release.
Now the snapshot ...I am really exhausted.
Thanks a lot
Best regards
Egle
Egle
Newbie
 
Posts: 6
Joined: Thu Nov 26, 2020 6:12 am

Next

Return to Support Forum

Who is online

Users browsing this forum: No registered users and 47 guests