Skip to content

Api process failed crash correlation#5586

Open
GittyHarsha wants to merge 7 commits into
MicrosoftEdge:mainfrom
GittyHarsha:api-process-failed-crash-correlation
Open

Api process failed crash correlation#5586
GittyHarsha wants to merge 7 commits into
MicrosoftEdge:mainfrom
GittyHarsha:api-process-failed-crash-correlation

Conversation

@GittyHarsha
Copy link
Copy Markdown
Contributor

No description provided.

GittyHarsha and others added 2 commits May 13, 2026 10:41
Adds CrashReport.md spec for the new ICoreWebView2StagingCrashReport
API that correlates WebView2 process failures with Watson crash reports.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Fix title from interface name to human-friendly 'Crash Report'
- Fix COM IDL code block language tag (cpp -> no tag)
- Fix WinRT/NET section headings to 'WinRT and .NET'
- Add __fastfail note: fields from WER event log, BucketId empty
- Add OOM exception code 0xe0000008 to ExceptionCode doc
- Soften CrashReportId dump filename claim
- Clean up BucketId doc (remove WER internal field names)
- Fix IsCustomCrashReportingEnabled: remove 'network hit' impl detail

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@GittyHarsha GittyHarsha requested a review from shrinaths May 13, 2026 09:14
Comment thread specs/CrashReport.md
Comment thread specs/CrashReport.md
Comment thread specs/CrashReport.md
Comment thread specs/CrashReport.md
@david-risney david-risney requested a review from aluhrs13 May 14, 2026 05:55
@GittyHarsha GittyHarsha marked this pull request as ready for review May 16, 2026 01:08
harshanp_microsoft and others added 5 commits May 25, 2026 17:35
- BucketId IS available at event-fire time for HTTP/Mac paths (handler
  completes upload before ProcessFailed fires). Remove stale 'network
  throttled/unavailable' case which implied it might not be.
- Add enterprise AAD WerReportSubmit as an explicit empty-BucketId case
  (no HTTP feedback channel, bucket never returned at event time).
- CrashReportId: soften 'locate the dump file' claim -- __fastfail crashes
  have no dump; CrashReportId still identifies the failure.
- Background: note that __fastfail produces no dump; CrashReportId still
  valid in that case.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
CrashReport is null for crashes that bypass the Crashpad crash handler
(__fastfail, heap corruption). These still fire ProcessFailed but do not
produce a crash report. Host apps that need data for those failure types
can query WER Event 1000 directly.

Remove WER event-log sourcing language from the summary and property docs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Replace 'minidump' with 'crash dump' throughout (heap dumps also possible)
- Remove implementation-detail language (no fastfail/heap corruption enumeration,
  no internal mechanism references)
- Remove field list from Background and Description intros
- Remove marketing noise from Background paragraph
- Add external kill as explicit null case
- Tighten null-case prose to be implementation-neutral
- Add dump filename hint (<CrashReportId>.dmp) to Background
- Update IDL comment to cover crash-type failures with no report
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants