Skip to content

fix(bug-report): include the crash minidump in crash-triggered reports (#2726)#700

Merged
inkeep-oss-sync[bot] merged 1 commit into
mainfrom
copybara/sync
Jul 20, 2026
Merged

fix(bug-report): include the crash minidump in crash-triggered reports (#2726)#700
inkeep-oss-sync[bot] merged 1 commit into
mainfrom
copybara/sync

Conversation

@inkeep-oss-sync

Copy link
Copy Markdown
Contributor

Copybara-translated 1 Inkeep OSS change. Rebase-merge this PR so the prepared commit lands directly on public main.

…s (#2726)

A crash-detected report invitation (boot-time dirty-shutdown/minidump scan
or a live render/child process death) is precisely a request to report a
crash, yet the crash-dump opt-in defaulted OFF, so crash reports usually
arrived without the minidump that triggered them (PRD-7403, split from
PRD-7394). The attach mechanism was fully wired; only the default did not
serve the crash-report case.

Make the crash-dump opt-in appear only when main confirms a minidump is on
disk for the event, and default it ON when it does:

- Thread an authoritative minidumpAvailable signal from main onto
  OkBugReportCrashDetectedEvent (only main can stat the crash-dumps dir).
  Boot events derive it from the freshness scan; process-gone events check
  the dir at arm time (best-effort: Crashpad may still be flushing).
- The report dialog renders the crash-dump row only when minidumpAvailable
  is true, defaults it checked, and sends includeCrashDump only then. A
  dump-less invite (e.g. a dirty shutdown with no native dump) shows no
  dead checkbox. Plain compose is unchanged and still carries no dump.

Consent is preserved without a silent send: the row stays a visible,
uncheckable checkbox, its note still states the memory is unredactable and
can contain document content, and nothing leaves the machine until the user
reviews the exact bundle (whose review card flags "crash dump not
redacted"). The no-silent-send invariant (N7) is kept.

NOTE FOR REVIEW: this flips the deliberately locked default-OFF from spec
2026-06-27-ok-report-bug-experience (R13f / OQ12 / D18), which lists
"defaulting minidump inclusion to ON" as an ASK_FIRST guardrail. Approved
by Andrew for the detected-crash + dump-available case specifically.

GitOrigin-RevId: 9027463f803660cee61c5bbcfcf4b4c2cf35f9da
@inkeep-oss-sync
inkeep-oss-sync Bot merged commit 05e299d into main Jul 20, 2026
@inkeep-oss-sync
inkeep-oss-sync Bot deleted the copybara/sync branch July 20, 2026 07:23
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.

1 participant