MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Help diagnosing issue with WebView2 on Server2012R2

Open
#2,122 9 comments 0 reactions 1 assignee View on GitHub

@champnic is already working on this.

Since Feb 2, 2022.

bug priority-low tracked
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Hello Experts,

My company has recently released our native C++ application with WebView2. It replaces the old IWebBrowser2 control. One of our users report that our application shows blank windows where the WebView2 controls should appear. I need a bit of guidance diagnosing the issue.

Here's what I know so far:
The user is running Server2012R2.
They claim there is no Citrix software installed
WebView2 is installed. The user is able to run the msedgewebview2 executable directly (i.e. outside of my application) and it displays a functional browser window.
My application successfully initializes WebView2 and calls Navigate to our URL. Calls to CreateCoreWebView2EnvironmentWithOptions, CreateCoreWebView2Controller, and ICoreWebView2::Navigate are all successful as far as my application can see.
Once my application appears, with blank windows where WebView2 should be, the user reports that no msedgewebview2.exe instances are running.
The user's $AppData/EBWebView folder has record of our URL appearing in browser history. A session cookie appears as well, so the browser sent and received a response.

So, apparently, the webview2 was functional long enough to make one request, but no longer exists by the time my user checks the task list. I guess it either crashed or was stopped. I could ask the customer to set up a DebugDiag rule to try to capture a crash, but I don't want to inconvenience them unless there is other evidence of a crash.

/edit The user's Crashpad\reports folder is empty, so I guess it was terminated some other way.

What logs can I look to for evidence of a crash or other termination?

Any other ideas or areas I can look into?

Thank you!

AB#38445884

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.