JCEF opens page only at second navigation

[Phylanx]

Hi!

One of our customers reported an issue opening a third party page with our chromium integration.
They try to navigate to a third party web server with our jcef integration and the first navigation fails.

In the logging at the problematic time we see the following problems:

Code: Select all

[33852:97728:1211/142405.042:ERROR:angle_platform_impl.cc(44)] vk_renderer.cpp:181 (rx::vk::(anonymous namespace)::VerifyExtensionsPresent): Extension not supported: VK_KHR_surface
[33852:97728:1211/142405.043:ERROR:angle_platform_impl.cc(44)] vk_renderer.cpp:181 (rx::vk::(anonymous namespace)::VerifyExtensionsPresent): Extension not supported: VK_KHR_win32_surface
[33852:97728:1211/142405.044:ERROR:angle_platform_impl.cc(44)] Display.cpp:1083 (egl::Display::initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-7): A requested extension is not supported, in ..\..\third_party\angle\src\libANGLE\renderer\vulkan\vk_renderer.cpp, rx::vk::Renderer::enableInstanceExtensions:1790.
[33852:97728:1211/142405.045:ERROR:gl_display.cc(497)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-7): A requested extension is not supported, in ..\..\third_party\angle\src\libANGLE\renderer\vulkan\vk_renderer.cpp, rx::vk::Renderer::enableInstanceExtensions:1790.
[33852:97728:1211/142405.045:ERROR:gl_display.cc(767)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[33852:97728:1211/142405.046:ERROR:gl_display.cc(801)] Initialization of all EGL display types failed.
[33852:97728:1211/142405.046:ERROR:gl_initializer_win.cc(135)] GLDisplayEGL::Initialize failed.


This logging is seen four times in total.
For more logging see

error.log

(7.17 KiB) Downloaded 869 times

(Can't upload whole log file because of security reasons).

Strange is that a retry of the navigation works, so it seems that something is fixed by the first call or some kind of backup mechanism is set in place afterwards.

Is this problem known to anybody?
How can we fix this?


This is our setup:

Windows 11/Windows Server 2016, 64 bit
JCEF 6723, 32 bit

[Phylanx]

After some time I could further analyze this problem.
It seems that the "Extension not supported: VK_KHR_surface" logging is not the problem.
This logging also occurs if loading the site works.

The problem is more that no JavaScript Callbacks via MsgRouterHandler are being transerred back into java ("MsgRouterHandler.onQuery").
We had similar problems earlier where the MsgRouterHandler never worked and installed a callback that always calls the MsgRouterHandler when they are installed.
Also this callback is missing.

It seems that the Binaries are loaded from a network drive, is it possible that this could cause the problem that the callback execution only works after the second invokation (and the binary had enough time to be loaded in the meanwhile)?

[Phylanx]

Further analysis:
Loading the libraries earlier doesn't change anything because the sub processes still also have to load them from the network share.
So we either have to have them locally or also do some kind of background preloading and navigation to e.g. chrome:version, so that the sub processes (renderer?,...) are initialized correctly in time.

Does anybody have an idea how to easily achieve this?

[magreenblatt]

Executing from a network share is generally a bad idea. Slow loading or silent failures/hangs can potentially cause any number of issues.