Problems of using JCEF with older Windows Version

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

Problems of using JCEF with older Windows Version

Postby Phylanx » Mon Aug 03, 2020 3:32 am

Hi!

We encounter severe problems at one of our customers using JCEF.
The behavior:

We initialize JCEF/CefApp and afterwards immediately call loadUrl to our desired URL destination.
As it seems the loadURL itself never happens (no calls comes to our nginx/application server that should respond to the call), the logs in the JCEF File is the following:

Code: Select all
[44496:39032:0710/110958.916:VERBOSE1:gpu_init.cc(215)] gl::init::InitializeGLNoExtensionsOneOff failed
[44496:39032:0710/110958.941:ERROR:mf_helpers.cc(14)] Error in dxva_video_decode_accelerator_win.cc on line 542
[44496:39032:0710/110958.947:ERROR:viz_main_impl.cc(197)] Exiting GPU process due to errors during initialization

So this seems to have something to do with GPU accelleration (log of mf_helpers indicates that).

After further analysis we found out the following:
We analyzed all logfiles of one day which were in total 3200 logfiles.
1151 logfiles had the logging above.
All these logfiles have been produced on OS versions "Windows 7" and "Windows Server 2008 R2".
On other OS versions ("Windows 10", "Windows 8.1", "Windows Server 2012 R2", "Windows Server 2016") this problem did not occur.
Unfortunatly we cannot reproduce this problem, we don't have these old outdated windows versions internally.

A rough google/forum search revealed only this (unresolved) thread: https://www.magpcss.org/ceforum/viewtop ... =6&t=17661
It seems that this also refers to Windows 7 but we don't have the "Windows versions earlier than 8 are not supported" logging.

This leads to my question(s):
1. Is it possible that something on these older OS versions causes this problem?
2. Is or was there a fix that handled this problem in newer versions?
3. Is there a workaround for this problem?
4. Is it likely that this problem will be fixed in nearer future for these older versions?

PS:
We're currently using JCEF version 3325 (applied some patches; planning to upgrade but not currently in scope) 32 bit on Windows OS (64 bit), java Version: Adopt OpenJDK 1.8.0_222.
We're not using OSR and not disabling GPU.
Phylanx
Expert
 
Posts: 201
Joined: Thu Aug 11, 2016 8:17 am

Re: Problems of using JCEF with older Windows Version

Postby magreenblatt » Mon Aug 03, 2020 11:04 am

Disabling GPU might fix the problem. I suggest you set up a Windows 7 machine for testing.
magreenblatt
Site Admin
 
Posts: 12382
Joined: Fri May 29, 2009 6:57 pm

Re: Problems of using JCEF with older Windows Version

Postby Phylanx » Tue Aug 11, 2020 1:18 am

We can't disable the GPU for that.
This problem happens only on outdated OS at the customer on a productive hospital system.
As we can't foresee the side effects of disabling GPU this won't happen.

As far as I see it now, we will stick with an accidentially found workaround.

Don't know if this helps someone, but I'll describe our usecase here:

We programmed something we call "preloading" for our application.
Loading our SPA web application (including login) can take a real long time.
We wanted to hide this from the user, so we prepare some browsers in the background to load this application and log in the current user.
The user can use the rest of our application in the meanwhile.
The preloading happens on a frame that is not visible to the customer (because it is in a non visible area of the screen) so the customer doesn't see anything.
With reparenting the window to our main application the preloaded browser can be used if the user wishes so.

After deactivating this preloading (browser,... is initialized at the time the user needs it) the problem never happened again.
For now we will stick with this workaround and hope a jcef upgrade will help us with the situation (which i don't think because there seems to be something fishy with GPU and older OS versions).
Ultimately the customer will have to upgrade his OS versions because they are anyways a huge security risk.

For us this problem is solved for now, thread can be closed.
Phylanx
Expert
 
Posts: 201
Joined: Thu Aug 11, 2016 8:17 am


Return to JCEF Forum

Who is online

Users browsing this forum: No registered users and 14 guests