Crash on Surface Pro X

[TonyValenti]

Hi All,
We've recently started having tickets come in regarding CEFx86 crashing on Surface Pro Xs. For additional information, Surface Pro Xs use an Arm64 processor but can run x86 apps virtualized.

Does anyone else have this same issue or the ability to test on the same hardware?

Faulting application name: CefSharp.BrowserSubprocess.exe, version: 79.1.350.0, time stamp: 0x5e30e1c7
Faulting module name: KERNELBASE.dll, version: 10.0.18362.387, time stamp: 0xfe0f5f59
Exception code: 0xe0000008
Fault offset: 0x0026bc20
Faulting process id: 0x1330
Faulting application start time: 0x01d5f325b624e0eb
Faulting application path: C:\Users\aklma\AppData\Local\Clio\app-20.2.28\x86\CefSharp.BrowserSubprocess.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll
Report Id: de141cf8-4856-47dc-9183-c49fbe9d8450
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: CefSharp.BrowserSubprocess.exe, version: 79.1.350.0, time stamp: 0x5e30e1c7
Faulting module name: KERNELBASE.dll, version: 10.0.18362.387, time stamp: 0xfe0f5f59
Exception code: 0xe0000008
Fault offset: 0x0026bc20
Faulting process id: 0x1330
Faulting application start time: 0x01d5f325b624e0eb
Faulting application path: C:\Users\aklma\AppData\Local\Clio\app-20.2.28\x86\CefSharp.BrowserSubprocess.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll
Report Id: de141cf8-4856-47dc-9183-c49fbe9d8450
Faulting package full name:
Faulting package-relative application ID:

[magreenblatt]

What CEF version? What is the symbolized call stack for the crash?

[amaitland]

Did you test with the CEF Sample application as I asked?

[TonyValenti]

What is a symbolized call stack and how do I get one?

[magreenblatt]

You get a symbolized call stack by downloading debug symbols for the exact CEF version that you’re using, and running with a debugger attached to your application.

[TonyValenti]

Thanks so much! I was actually able to demonstrate the issue pretty easily and I think the crash is a side effect of something else at play.

THIS ONLY AFFECTS ARM64 PROCESSORS.

Take a look at this:
https://www.youtube.com/watch?v=JrhvjskhZk0

On an ARM64 processor, going to https://app.clio.com in the minimal example causes CEF to become non-responsive - infact you can see it stop rendering and one of the browser subprocesses goes away. It works in Edge (Arm64 on Arm64) and Chrome (x86 on Arm64 - just like CEF). The issue demonstrated in the video does not cause an event log crash error to occur.

The computer Im demonstrating the video on is a completely isolated Suface Pro X that I bought this weekend specifically so we could do the testing. I have it configured for remote access via TeamViewer. Is there a way for me to privately send you the login credentials? This will save you from having to go buy a surface as well.

[magreenblatt]

Please post the requested call stack.

[TonyValenti]

Hi @Magreenblatt,
On ARM64, it does not create an event log entry nor does it appear to technically crash. The process silently dies.

[magreenblatt]

What architecture is the Chrome version that you’re running (x86, x64 or ARM64)? What architecture is the CEF version?

[TonyValenti]

Hi MaGreenBlat,
CEF = x86 on ARM64 (Does not work)
Chrome = x86 on ARM64 (Same as above = Does work)