Crash on Surface Pro X

[amaitland]

Have you checked the log file?
Have you tested with the CEF Sample application? This is not the same as the CefSharp minimum example. There are details in https://github.com/cefsharp/CefSharp/bl ... bug-report which I've already linked you.

What version of Chrome have you tested with? Comparing CEF vs chrome at different versions is not all that meaningful.

From what I can tell the ARM64 emulation for x86 is not particularly mature, if something is crashing in the kernel then you likely need Microsoft to actually fix.

Make sure you have Windows 10 fully patched.

[TonyValenti]

Hi Amaitland,
Thanks so much for your patience as I figure this process out!
1. Windows 10 v 1909 ARM64 fully patched with all updates.

2. Running the CEF Sample Application (x86) on ARM64 (with no command line parameters) works as expected.

3. Running the CEF Sample Application (x86) on ARM64 as so:
cefclient --multi-threaded-message-loop --off-screen-rendering-enabled --enable-gpu
Does not seem to render anything to the screen. Browsing to https://app.clio.com does not result in anything being output to the log

4. Chrome 80.0.3987.132 (Official Build) (32-bit) on ARM64 works as expected.

5. Running CEF Sharp Minimal Example (x32) with WPF does not work as expected and outputs the following to debug.log:
[0307/193236.915:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: browser
[0307/193237.670:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: gpu-process
[0307/193238.366:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: utility
[0307/193241.676:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: renderer
[0307/193247.150:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: renderer
[0307/193248.093:ERROR:validation_errors.cc(76)] Invalid message: VALIDATION_ERROR_UNEXPECTED_NULL_POINTER (null field 1)

I think I got everything you need. If I missed something, please let me know.

[TonyValenti]

Hi All,
Is there any additional information that you might need?

[magreenblatt]

Hi All,
Is there any additional information that you might need?

We're not going to be able to debug this problem for you. You (or Microsoft) will need to do the debugging and report back with your findings.

[ndesktop]

VALIDATION_ERROR_UNEXPECTED_NULL_POINTER looks like a mojo error.

You need to run with --enable-logging --v=1 (2, ...) to spot who makes what call (most likely is an IPC which is sent with nullptr from caller and the receiver expects a non-nullptr).
Since this can be everything, start by tweaking the command line, especially gpu and offscreen related and maybe you are lucky.

Otherwise, fire up the debugger, read this, perhaps install VsChromium extension, reproduce the bug under debugger, then start the hunt for Red October. You will probably see and offending IPC buffer, lookup the message, search in code for the message where is sent, consult the Chromium issues list for something that looks similar etc.

[TonyValenti]

Is there a bounty I can fund to get resolution on this? We have a device that we've purchased so we can consistently recreate the issue. It would be great if I could give remote access to someone and pay them to solve it.

[amaitland]

See https://aka.ms/user-mode-dump-files-howto for generic windows instructions on getting a dump file.

Try removing the `--enable-gpu` command line arg.

If the problem only occurs when using --off-screen-rendering-enabled then you can try `CefSharp.MinimalExample.Winforms`, perhaps you can use
`WinForms` hosted in `WPF`.

As it works on native Intel 32bit and WOW64 then Microsoft probably need to fix their Intel 32bit emulation on ARM64.