MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: empty Crashpad reports directory when crashing

Open
#4,382 10 comments 0 reactions 1 assignee View on GitHub

@LiangTheDev is already working on this.

Since Feb 20, 2024.

Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

My understanding is that crash reporting is enabled by default.

If I start my app, open Task Manager and kill the browser process (--embedded-browser-webview) or the renderer process (--type=renderer), the ProcessFailed event is raised, but I don't see any reports getting created.

IsCustomCrashReportingEnabled is set to false (though I don't think that matters for your purposes) and FailureReportFolderPath is set to %localappdata%\\<appName>\\EBWebView\\Crashpad\\reports

However, the reports directory is empty.
The only modified file after the crash is settings.dat.

Seems related to this issue (maybe that's answered and I'm just not understanding the resolution)

--
though I see this in Edge too assuming I'm following the steps correctly. Maybe it's expected that we don't create dumps in these cases?

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

121.0.2277.128

SDK Version

1.0.2277.86

Framework

Winforms

Operating System

Windows 10

OS Version

10.0.19045 Build 19045

Repro steps

see above

Repros in Edge Browser

Yes

Regression

Don't know

Last working version (if regression)

No response

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.