MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Better WebView2 crash/debugging support needed
Open
@champnic is already working on this.
Since Nov 12, 2021.
feature request
tracked
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
After using WebView2 for an applications with high quality standards, I'm sure that Microsoft could work to improve on the following:
- better if WebView2 browser process creates a dump for every crash, instead of just reporting a “ProcessFailed” event. The “ProcessFailed” event should also contain more relevant details that could help on fixing. A recovery after a crash is a “no go” for us, we can just crash our application.
- better if the WebView2 have a flag to enable a “debug” logging (add logging hook for WebView2), so that we could understand the possible reasons for a crash, or do some improvements on our side based on how the WebView2 handles different situations.
- better documentation and availability of the “.pdb” files needed for the WebView2. Path to PDBs and a “how to”. On an application crash dump, the .pdb's for WebView2 couldn' be retrieved.
- better documentation needed for threading regarding browser calls, javascript interaction & events.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.