WebView2Feedback icon indicating copy to clipboard operation
WebView2Feedback copied to clipboard

Content not loading after updating to runtime 99.0.1150.39 (evergreen)

Open fdzatdtv opened this issue 3 years ago • 5 comments

Description One of our customers can't work after runtime updated to 99.0.1150.39 (evergreen). The content is not loading any more. The area of the webview is grey. Our product hasn't changed. Replacing the runtime by 94.0.992.31 fixes the problem. The 94.* is the last one working version. All newer versions fail too. We load the content by setting the Source property to a local html file (url = file://...). The application is accessed via RDP.

Version SDK: 1.0.1054.31 Runtime: Evergreen 99.0.1150.39 Framework: WinForms (x86) OS: Windows Server 2016 Standard

Repro Steps To prove that it hasn't to do with our productive code, we implemented a mini sample capable of loading certain targets or a local file. Interestingly, on our test systems and many other customers it works with both runtimes, but at one customer it works only with 94.0.992.31 and fails with 99.0.1150.39. To prove the difference we replaced the contents of the evergreen installation (99.0.1150.39) with the contents of the fixed version (94.0.992.31). Compile solution, start it, click on "Test load..." and then on "Load".

WV2Checker.zip

Screenshot of working examples Works94Google

Screenshot of failing examples Fails99Google

Additional context

AB#38686524

fdzatdtv avatar Mar 16 '22 10:03 fdzatdtv

@fdzatdtv try to reinstall the runtime of webview2

jarno9981 avatar Mar 16 '22 18:03 jarno9981

@fdzatdtv Thanks for the bug report, and sorry you're customer is hitting this.

To confirm:

  1. This started happening with Edge 95?
  2. This only happens for the one customer, or for all customers?
  3. Is there any error returned from the functions?
  4. If you turn on Narrator, is it able to see and navigate to the expected web content?

My hunch is that this might have something to do with the graphics driver and settings on that particular machine. If you want, you can try disabling some GPU changes with the following browser arguments: --ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds If that resolves the issue, then that would indicate a graphics driver issue.

champnic avatar Mar 16 '22 23:03 champnic

  1. This started happening with Edge 95?

Yes.

  1. This only happens for the one customer, or for all customers?

Only for one.

  1. Is there any error returned from the functions?

No.

  1. If you turn on Narrator, is it able to see and navigate to the expected web content?

I've only seen Narrator for Windows 10 or 11. Is this also available for Windows Server 2016?

My hunch is that this might have something to do with the graphics driver and settings on that particular machine. If you want, you can try disabling some GPU changes with the following browser arguments: --ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds If that resolves the issue, then that would indicate a graphics driver issue.

By setting the browser arguments from above, the desired content is loaded with the runtime 99.*. So, probably this can pinpoint the problem.

fdzatdtv avatar Mar 24 '22 10:03 fdzatdtv

Here's a screenshot of the graphic driver details: GraphicDriver

fdzatdtv avatar Mar 24 '22 10:03 fdzatdtv

Thanks for the info! I've added this bug to our backlog.

champnic avatar Mar 25 '22 22:03 champnic