-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPF - blank screen when GPU acceleration disabled #3337
Comments
As per https://github.com/cefsharp/CefSharp/blob/master/.github/ISSUE_TEMPLATE/bug_report.md Any problem that reproduces with cefclient needs to be fixed in CEF. Is there a reason you need to disable GPU acceleration? |
The @EMJagadeesh What As this problem is likely At this point my only suggestion would be to also disable settings.CefCommandLineArgs.Add("disable-gpu");
settings.CefCommandLineArgs.Add("disable-gpu-compositing"); |
@amaitland - Issue resolve after disable GPU |
@EMJagadeesh Thanks for confirming. |
Hi,
I've found a possible inconsistency in cef sharp 86.0.241 in our application. when DisableGpuAcceleration in CefSettings and launch the application, it open with blank html UI when I minimize it and restore it, html UI will load in the application.
What version of the product are you using?
86.0.241
What architecture x86 or x64?
x64
On what operating system?
Win10 Enterprise
Are you using
WinForms
,WPF
orOffScreen
?WPF
What steps will reproduce the problem?
What is the expected output? What do you see instead?
Expected Output:
When DisableGpuAcceleration in CefSettings and launch the application, html page load properly without any blank page
Actual Output:
When DisableGpuAcceleration in CefSettings and launch the application, html page load properly with blank page
Please provide any additional information below.
Please find the faced blank page while launching the application
Does this problem also occur in the
CEF
Sample Application from http://opensource.spotify.com/cefbuilds/index.html?Yes
Thanks,
Jagadeesh
The text was updated successfully, but these errors were encountered: