v129 - Invalid file descriptor to ICU data received

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.

v129 - Invalid file descriptor to ICU data received

Postby dmccracken » Wed Oct 16, 2024 8:17 am

After building v129, we can run cefclient successfully within the associated output directory (Release_GN_X86).

When we move it along with the various dependent files, cefclient crashes while loading, and the debug log file shows:

[1014/145211.559:WARNING:main_context_impl.cc(109)] Chrome runtime defaults to the Views framework.
[1014/145211.559:WARNING:main_context_impl.cc(130)] Using Chrome style; Views-hosted window; Windowed rendering (not a warning)
[1014/145211.563:ERROR:icu_util.cc(223)] Invalid file descriptor to ICU data received.
[1014/145211.563:FATAL:icu_util.cc(297)] Check failed: result.

I've tried copying lots of other files from the output directory but cefclient still will not run anywhere except the output directory itself. We have never experienced this issue with any other builds in the past.

Any thoughts?
dmccracken
Newbie
 
Posts: 3
Joined: Wed Oct 16, 2024 8:06 am

Re: v129 - Invalid file descriptor to ICU data received

Postby magreenblatt » Wed Oct 16, 2024 11:04 am

You should use a binary distribution. Download from https://cef-builds.spotifycdn.com/index.html or follow the build instructions at https://bitbucket.org/chromiumembedded/ ... ldSetup.md
magreenblatt
Site Admin
 
Posts: 12968
Joined: Fri May 29, 2009 6:57 pm

Re: v129 - Invalid file descriptor to ICU data received

Postby dmccracken » Wed Oct 16, 2024 11:25 am

Thanks. We can't use the binary distributions since we require support for codecs/mpeg.

I've been following the process defined on this page for years and have never had any issues: https://bitbucket.org/chromiumembedded/ ... ckStart.md
Of course we include the following for the codec support:
proprietary_codecs=true ffmpeg_branding=Chrome
dmccracken
Newbie
 
Posts: 3
Joined: Wed Oct 16, 2024 8:06 am

Re: v129 - Invalid file descriptor to ICU data received

Postby magreenblatt » Wed Oct 16, 2024 11:43 am

I've been following the process defined on this page for years and have never had any issues

MasterBuildQuickStart instructions are for local developer builds. You should follow the instructions on the AutomatedBuildSetup page to create your own binary distribution.
magreenblatt
Site Admin
 
Posts: 12968
Joined: Fri May 29, 2009 6:57 pm

Re: v129 - Invalid file descriptor to ICU data received

Postby dmccracken » Thu Oct 17, 2024 10:11 am

We are not distributing the binaries to others, so the automated process isn't of much concern at this time.
Are you aware of anything that may be affecting the access to the ICU data file?
Again, I built previous versions on this same machine with the same process (using VS2022 and the 10.0.22621.2428 SDK and had no issues.
The PC is 64-bit Win 11 and I'm building a release version for x86.

Thanks for any assistance you can provide.

Dave
dmccracken
Newbie
 
Posts: 3
Joined: Wed Oct 16, 2024 8:06 am

Re: v129 - Invalid file descriptor to ICU data received

Postby magreenblatt » Thu Oct 17, 2024 10:16 am

The important detail here is not that you automate the build. It's that you use the correct build configuration for builds that are not just local developer builds.
magreenblatt
Site Admin
 
Posts: 12968
Joined: Fri May 29, 2009 6:57 pm


Return to Support Forum

Who is online

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