BriskBard, CEF4Delphi, WebView4Delphi, WebUI4Delphi and WebUI4CSharp

Ok, will do that and post the results here soon.

Just tested with the official CEF client and the crash happens.

I recorded a video :

https://easyupload.io/n5ixqu

Note that right after selecting the image file to upload, the client closes by itself.

That means that this might be an issue in the CEF library or that PC configuration has some incompatibility with Chromium.
I see that you posted this information in the CEF forum too and they will need the call stack of the crash.

Follow this guide to get the call stack :
https://www.briskbard.com/forum/viewtopic.php?f=10&t=1050

Ok, i will do the steps to generate the call stack.

Actually the crash happens not only on this machine, it's a lot of other machines although not all.

After running the command from windbg, i'm getting this error ; any idea ? The file is on the correct path

SYMSRV: BYINDEX: 0x2
c:\symbols*http://msdl.microsoft.com/download/symbols
libcef.dll.pdb
A9ABF1E7264327614C4C44205044422E1
SYMSRV: PATH: c:\symbols\libcef.dll.pdb\A9ABF1E7264327614C4C44205044422E1\libcef.dll.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP: c:\symbols\libcef.dll.pdb\A9ABF1E7264327614C4C44205044422E1\libcef.dll.pdb - file system or network error reading pdb
DBGHELP: C:\Users\MTECH-WINDOWS_10\Desktop\cef_binary_105.3.38+g2a6a54b+chromium-105.0.5195.102_windows64_client\Release\libcef.dll.pdb - file not found
DBGHELP: libcef.dll.pdb - file not found
*** WARNING: Unable to verify checksum for C:\Users\MTECH-WINDOWS_10\Desktop\cef_binary_105.3.38+g2a6a54b+chromium-105.0.5195.102_windows64_client\Release\libcef.dll
DBGHELP: libcef - export symbols

************* Symbol Loading Error Summary **************
Module name Error
libcef 0xc00 - thread
0:000> .reload /f libcef.dll
SYMSRV: BYINDEX: 0x3
c:\symbols*http://msdl.microsoft.com/download/symbols
libcef.dll.pdb
A9ABF1E7264327614C4C44205044422E1
SYMSRV: PATH: c:\symbols\libcef.dll.pdb\A9ABF1E7264327614C4C44205044422E1\libcef.dll.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP: c:\symbols\libcef.dll.pdb\A9ABF1E7264327614C4C44205044422E1\libcef.dll.pdb - file system or network error reading pdb
DBGHELP: C:\Users\MTECH-WINDOWS_10\Desktop\cef_binary_105.3.38+g2a6a54b+chromium-105.0.5195.102_windows64_client\Release\libcef.dll.pdb - file system or network error reading pdb
DBGHELP: libcef.dll.pdb - file not found
*** WARNING: Unable to verify checksum for C:\Users\MTECH-WINDOWS_10\Desktop\cef_binary_105.3.38+g2a6a54b+chromium-105.0.5195.102_windows64_client\Release\libcef.dll
DBGHELP: libcef - export symbols

************* Symbol Loading Error Summary **************
Module name Error
libcef 0xc00 - thread

The call stack needed to debug this issue appears when the EXE crashes and you click on the "View -> Call Stack" menu in WinDbg.

Then use the "Edit -> Copy Window Text To Clipboard" menu option to copy the call stack to the clipboard.

The command i referred on the previous post (and the one i pasted the error log) is this :

.reload /f libcef.dll

I could not get the 'symbolized' call stack yet.

After that step you need to move the PDB file to the right directory inside c:\symbols\libcef.dll.pdb\
Then close WinDbg and open it again. Select cefclient in the “File->Open executable” menu option and press F5 to run cefclient.

At that point you need to reproduce the steps that cause this issue until cefclient crashes or freezes. Then select the "View -> Call Stack" menu option.

I tried to reproduce this issue in a different computer with an integrated Intel graphics card and everything worked correctly.

It's a tricky one... so far i have about 8 complains of customers, i entered some of them in Teamviewer and could reproduce the crash with the official CEF client after 102. Will keep searching.