Replies: 1 comment 2 replies
-
Converting to discussion as this is unlikely a bug in CefSharp as it works correctly on every other platform tested. Sounds like a problem with the Intel driver. Did you try the disabling WPF hardware acceleration?
Likely safe to ignore as crash reporting is unrelated to rendering. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What version of the product are you using?
93.1.111, 92.0.260 (67.0.0 works fine)
What architecture x86 or x64?
x86, x64, AnuCPU
What version of .Net?
.Net 4.5.2, Net 4.6.2
On what operating system?
Win10
Are you using
WinForms
,WPF
orOffScreen
?WPF (WinForms, OffScreen work fine)
What steps will reproduce the problem?
Run MinimalExample WPF.
Type into google search bar.
Nothing happen.
Latest versions of CefSharp WPF work very poorly on the i5-11600 (driver with WPF fix is installed, any other WPF works perfectly fine). I've tested it on different PCs, so it's most likely not an environment issue. It works fine with WinForms and OffScreen as well as WPF version 67.0.0. It works fine with the latest WPF version on all other CPUs I've tried (older ones), and on i5-11600 via RPD with another CPU. This is a rendering issue, when I type something in the google search bar, the input is not shown. But after resizing the window, the input appears as well as the dropdown. There is only one error message in the output on the start
[0913/174644.236:ERROR:crashpad_client_win.cc(520)] CreateProcess: The system cannot find the file specified. (0x2)
. But there is the same message for WinForms and everething works fine.For my application, I am using our internal web controls and they are not showing at all. I tried one weird fix: set a timer to resize the window by 1 pixel every 100ms in order to call the render operation. Of course I can't use this fix, but in this case it renders everything fine.
Yep, I understand that this is a hardware problem, but version 67.0.0 is working fine, so I hope there is something that can be fixed.
Does this problem also occur in the
CEF
Sample ApplicationNo
Beta Was this translation helpful? Give feedback.
All reactions