JCEF Crash in igxelpicd32.dll

[Phylanx]

Hi!

Our customer recently reported crashes of our application while watching PDFs with JCEF.
The problem occurs sporadically but is relatively easily reproducible on customers PCs but not on our development environments.

The event crash code looks like the following:

Code: Select all

Fehlerhafter Anwendungsname: javaw.exe, Version: 8.0.4320.6, Zeitstempel: 0x6710e06e
Fehlerhafter Modulname: igxelpicd32.dll, Version: 32.0.101.6881, Zeitstempel: 0x6840b05c
Ausnahmecode: 0xc000041d
Fehleroffset: 0x000547e3
Fehlerhafte Prozess-ID: 0x5B30
Fehlerhafte Anwendungsstartzeit: 0x1DC41851ED2969C
Fehlerhafter Anwendungspfad: C:\CGM\CGM_MPA_VLKH\tools\jdk1.8.0_432\jre\bin\javaw.exe
Fehlerhafter Modulpfad: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_c0f9af7de2d619a0\igxelpicd32.dll
Berichts-ID: 8ba95a51-5fd1-4442-bd5d-315c51371d38
Vollständiger Name des fehlerhaften Pakets:
Fehlerhafte paketbezogene Anwendungs-ID:


Our environment:
OS: Win11 (but also earlier happened with Win10)
Java: Adopt OpenJDK 1.8.0_432, 32 bit
JCEF info: version 130 32bit (but already happened with version 84 32bit).

Thx for your help!

[ndesktop]

This is an Intel graphics driver dll. The exception is STATUS_FATAL_USER_CALLBACK_EXCEPTION, which is a usually a noncontinuable exception, probably meaning an exception was raised from inside an exception handler.
There is nothing CEF (or anything else using it) can do since this is inside an Intel dll. Best bet would be a driver update, or launch it without hardware acceleration to check if the issue still reproduce, or patch vulkan to blacklist this dll (long shot) and do a custom build (I had to do this for RIVA tuner dll which crashed on many systems on a product using CEF I work on).

[Phylanx]

OK, thanks so far.
We'll try it with the disable gpu.

Am I right that I need to pass the flags "--disable-gpu" and "--disable-gpu-compositing"?
is it possible to pass the flags when calling CefApp.init or do I have to add a "command_line->AppendSwitch" in client_app.cpp?

[ndesktop]

OK, thanks so far.
We'll try it with the disable gpu.

Am I right that I need to pass the flags "--disable-gpu" and "--disable-gpu-compositing"?
is it possible to pass the flags when calling CefApp.init or do I have to add a "command_line->AppendSwitch" in client_app.cpp?

Yes, pass these flags or use OnBeforeCommandLineProcessing to call AppendSwitch.

[Phylanx]

Hi again!

We have gathered some additional information.
Colleagues activated crash dumps for java.exe, so we got a windows crash dump.
The 0xc000041d is caused by a c0000005 (Access Violation).
Analysis with WinDBG showed the following stack:

PROCESS_NAME: javaw.exe

READ_ADDRESS: 00021030

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00021030

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
3a3df17c 539c373f 00000000 3e7f0c78 3e7f0c78 igxelpicd32+0x547e3
3a3df190 53a74a07 00000000 45f87030 00000000 igxelpicd32!DrvValidateVersion+0x16a7f
3a3df1b0 5383407a 45f87030 77613bd0 00000000 igxelpicd32!DrvValidateVersion+0xc7d47
3a3df1d0 54357b8e 000906e8 766dc0b0 fb010dca igxelpicd32!DumpRegistryKeyDefinitions+0xee9a
3a3df2ec 539aa7d6 00000002 00000000 00000000 igxelpicd32!DrvValidateVersion+0x9aaece
3a3df328 69b76f2a fb010dca 00000002 fb010dca igxelpicd32!DrvSetPixelFormat+0x196
3a3df344 69b902bb 45e4c020 fb010dca 00000000 opengl32!__DrvSetPixelFormat+0x4f
3a3df42c 75a631fb fb010dca 00000002 3a3df4b8 opengl32!wglSetPixelFormat+0x19b
3a3df44c 69cb42b1 fb010dca 00000002 3a3df4b8 gdi32full!SetPixelFormat+0x3b
3a3df4f4 69ceb90e 38383764 38383760 d0e1704c awt!Java_sun_awt_windows_WButtonPeer_setLabel+0x327
3a3df578 77629b23 000900fc 00009800 00000000 awt!Java_sun_awt_windows_WTextFieldPeer_setEchoChar+0x287e
3a3df5a4 77617c9d 69ceb590 000900fc 00009800 user32!_InternalCallWinProc+0x2b
3a3df6a0 00000000 00000000 00000000 00000000 user32!UserCallWinProcCheckWow+0x49d

I also attached the whole WinDBG analysis in a txt file:

WinDbg_analysis.txt

(7.73 KiB) Downloaded 73 times

Just for the case anyone else searches for it.
Unfortunatly we couldn't reproduce the problem with detailed MainFrame, the problem occurs only on customer side alone and I do not dare hacking something into our customers system (hospital O_O).

Our further steps are changing the standard intel driver to the default windows graphics driver and hoping to not reproduce it
If that doesn't work we'll have to try disabling the GPU or hope that intel fixes the bug.

Thanks again for your help!