Cefsharp cannot render properly unless I drag the border of the window

[KYRIENIU1]

Is there an existing issue for this?

• I have searched both open/closed issues, no issue already exists.

CefSharp Version

137.0.100

Operating System

Windows 10

Architecture

x64

.Net Version

.net5

Implementation

WPF

Reproduction Steps

I used cefsharp.wpf.netcore. in wpf to make a local browser, but the exe that can run normally in other environments cannot render normally in the win10 LTSL 2018 environment, and even the scroll bar cannot be used normally. Only when I drag the boundary of the window to change can my previous operation be rendered normally. But there are no error messages in p's log,

Expected behavior

英语
I used cefsharp.wpf.netcore. in wpf to make a local browser, but the exe that can run normally in other environments cannot render normally in the win10 LTSL 2018 environment, and even the scroll bar cannot be used normally. Only when I drag the boundary of the window to change can my previous operation be rendered normally. But there are no error messages in p's log,

Actual behavior

英语
I used cefsharp.wpf.netcore. in wpf to make a local browser, but the exe that can run normally in other environments cannot render normally in the win10 LTSL 2018 environment, and even the scroll bar cannot be used normally. Only when I drag the boundary of the window to change can my previous operation be rendered normally. But there are no error messages in p's log,

Regression?

No response

Known Workarounds

No response

Does this problem also occur in the CEF Sample Application

Yes using WPF/OffScreen command line args

Other information

No response

[KYRIENIU1]

The winform version can be used normally, but the wpf.netcore version will have problems such as being stuck in the interface and being unable to switch interfaces. But my program is wpf and will have various flashing problems when using winform.

[amaitland]

More likely this is an issue with your GPU drivers than a CefSharp bug.

e.g. dotnet/wpf#3817

[KYRIENIU1]

But even if I set to disable Gpu, this phenomenon still exists