Invalid file descriptor to ICU data received

Having problems with building or using the JCEF Java binding? Ask your questions here.

Invalid file descriptor to ICU data received

Postby datlong1502 » Thu Nov 24, 2016 9:31 pm

Hi all.
I am newbie on JCEF. when i am trying run jcef-example. i catch following error.
error: Invalid file descriptor to ICU data received
error: Illegal instruction LD_PRELOAD=$LIB_PATH/libcef.so java -cp "$CLS_PATH" -Djava.library.path=$LIB_PATH tests.$RUN_TYPE.MainFrame "$@"

please help me resolve this. thanks.
datlong1502
Newbie
 
Posts: 2
Joined: Tue Nov 22, 2016 10:10 am

Re: Invalid file descriptor to ICU data received

Postby binhucsd » Mon Mar 06, 2017 4:36 pm

By following doccument from https://bitbucket.org/chromiumembedded/ ... ndBuilding
to build and install it.
After having build the JCEF Java classes on GNU/linux x86_64 with:

JCEF Version = 3.2924.152
CEF Version = 3.2924.1572
Chromium Version = 56.0.2924.76
, I got this error when running the run test script:
[0306/133518.511087:ERROR:icu_util.cc(173)] Invalid file descriptor to ICU data received.
Please help me.
binhucsd
Newbie
 
Posts: 1
Joined: Mon Mar 06, 2017 4:28 pm

Re: Invalid file descriptor to ICU data received

Postby Kremio » Thu Apr 27, 2017 9:54 am

Hi!

I'm having the exact same problem.
After some googling, I tried to copy the files icudtl.dat, natives_blob.bin and snapshot_blob.bin from /jcef_build/native/Release/ to /usr/bin/ but that did not help...

Did anyone find a solution?
Kremio
Newbie
 
Posts: 5
Joined: Thu Apr 20, 2017 4:23 am

Re: Invalid file descriptor to ICU data received

Postby magreenblatt » Thu Apr 27, 2017 11:07 am

Pay attention to the build output. You should see something like:

*** Run the following commands manually to create necessary symlinks ***"
sudo ln -s ${CEF_RESOURCE_DIR}/icudtl.dat ${JAVA_DIR}/jre/bin/icudtl.dat"
sudo ln -s ${CEF_BINARY_DIR}/natives_blob.bin ${JAVA_DIR}/jre/bin/natives_blob.bin"
sudo ln -s ${CEF_BINARY_DIR}/snapshot_blob.bin ${JAVA_DIR}/jre/bin/snapshot_blob.bin"

The ${} values will be the actual values required by your system when you build.
magreenblatt
Site Admin
 
Posts: 12384
Joined: Fri May 29, 2009 6:57 pm

Re: Invalid file descriptor to ICU data received

Postby f4n » Mon May 08, 2017 9:28 am

Hi,
i saw this build output and executed the commands but i have the same problem. Any further ideas?

Code: Select all
#> ./run.sh linux64 Release detailed
Offscreen rendering enabled
Using:
JCEF Version = 3.3029.154
CEF Version = 3.3029.1604
Chromium Version = 58.0.3029.81
CefApp: INITIALIZING
initialize on Thread[AWT-EventQueue-0,6,main] with library path /home/f4n/Tools/java-cef/src/jcef_build/native/Release
Added scheme search://
Added scheme client://
[0508/161959.743922:ERROR:icu_util.cc(173)] Invalid file descriptor to ICU data received.
./run.sh: Zeile 37: 29248 Trace/breakpoint trap   (Speicherabzug geschrieben) LD_PRELOAD=$LIB_PATH/libcef.so java -cp "$CLS_PATH" -Djava.library.path=$LIB_PATH tests.$RUN_TYPE.MainFrame "$@"


Code: Select all
*** Run the following commands manually to create necessary symlinks ***
sudo ln -s /home/f4n/Tools/java-cef/src/third_party/cef/cef_binary_3.3029.1604.g364cd86_linux64/Resources/icudtl.dat /usr/java/latest/jre/bin/icudtl.dat
sudo ln -s /home/f4n/Tools/java-cef/src/third_party/cef/cef_binary_3.3029.1604.g364cd86_linux64/Release/natives_blob.bin /usr/java/latest/jre/bin/natives_blob.bin
sudo ln -s /home/f4n/Tools/java-cef/src/third_party/cef/cef_binary_3.3029.1604.g364cd86_linux64/Release/snapshot_blob.bin /usr/java/latest/jre/bin/snapshot_blob.bin


Code: Select all
#> ll /usr/java/latest/jre/bin/
insgesamt 452
lrwxrwxrwx 1 root root      8 15. Mär 09:39 ControlPanel -> jcontrol
lrwxrwxrwx 1 root root    108  8. Mai 16:12 icudtl.dat -> /home/f4n/Tools/java-cef/src/third_party/cef/cef_binary_3.3029.1604.g364cd86_linux64/Resources/icudtl.dat
-rwxr-xr-x 1 root root   7734 15. Mär 09:39 java
-rwxr-xr-x 1 root root 127897 15. Mär 09:39 javaws
-rwxr-xr-x 1 root root   6264 15. Mär 09:32 jcontrol
-rwxr-xr-x 1 root root   7941 15. Mär 09:39 jjs
-rwxr-xr-x 1 root root   7941 15. Mär 09:39 keytool
lrwxrwxrwx 1 root root    112  8. Mai 16:17 natives_blob.bin -> /home/f4n/Tools/java-cef/src/third_party/cef/cef_binary_3.3029.1604.g364cd86_linux64/Release/natives_blob.bin
-rwxr-xr-x 1 root root   8149 15. Mär 09:39 orbd
-rwxr-xr-x 1 root root   7957 15. Mär 09:39 pack200
-rwxr-xr-x 1 root root   7997 15. Mär 09:39 policytool
-rwxr-xr-x 1 root root   7941 15. Mär 09:39 rmid
-rwxr-xr-x 1 root root   7949 15. Mär 09:39 rmiregistry
-rwxr-xr-x 1 root root   7965 15. Mär 09:39 servertool
lrwxrwxrwx 1 root root    113  8. Mai 16:17 snapshot_blob.bin -> /home/f4n/Tools/java-cef/src/third_party/cef/cef_binary_3.3029.1604.g364cd86_linux64/Release/snapshot_blob.bin
-rwxr-xr-x 1 root root   8181 15. Mär 09:39 tnameserv
-rwxr-xr-x 1 root root 228933 15. Mär 09:39 unpack200
f4n
Newbie
 
Posts: 3
Joined: Mon May 08, 2017 9:21 am

Re: Invalid file descriptor to ICU data received

Postby magreenblatt » Mon May 08, 2017 1:10 pm

What Linux distribution and JVM name/version are you using?
magreenblatt
Site Admin
 
Posts: 12384
Joined: Fri May 29, 2009 6:57 pm

Re: Invalid file descriptor to ICU data received

Postby f4n » Tue May 09, 2017 2:20 am

I'm using Oracle Java 1.8.0_121 and Fedora 25.
f4n
Newbie
 
Posts: 3
Joined: Mon May 08, 2017 9:21 am

Re: Invalid file descriptor to ICU data received

Postby f4n » Tue May 09, 2017 2:32 am

Ok, i found the problem. Thank you for your hint! I had a different java version in my PATH variable (different to JAVA_HOME).
The problem here is the build output used the JAVA_HOME path to set the symlinks but the "./run ..." command is using the java binary configured in the PATH variable.

Improvment suggestion: the run script should use the java binary from JAVA_HOME like the build scripts.
f4n
Newbie
 
Posts: 3
Joined: Mon May 08, 2017 9:21 am

Re: Invalid file descriptor to ICU data received

Postby magreenblatt » Tue May 09, 2017 9:17 am

f4n wrote:Ok, i found the problem. Thank you for your hint! I had a different java version in my PATH variable (different to JAVA_HOME).
The problem here is the build output used the JAVA_HOME path to set the symlinks but the "./run ..." command is using the java binary configured in the PATH variable.

Improvment suggestion: the run script should use the java binary from JAVA_HOME like the build scripts.

Can you add a JCEF issue for the improvement? Thanks.
magreenblatt
Site Admin
 
Posts: 12384
Joined: Fri May 29, 2009 6:57 pm


Return to JCEF Forum

Who is online

Users browsing this forum: No registered users and 17 guests