Closed Bug 1874235 Opened 1 year ago Closed 1 year ago

Windows Error Reporting can fail in several ways

Categories

(Toolkit :: Crash Reporting, defect)

defect

Tracking

()

RESOLVED FIXED
125 Branch
Tracking Status
firefox-esr115 --- fixed
firefox124 --- fixed
firefox125 --- fixed

People

(Reporter: gsvelto, Assigned: gsvelto)

References

Details

Attachments

(2 files)

While analyzing the WER interceptor we found several issues that prevent it from working correctly:

  • The logic parsing the command-line arguments for child process crashes stopped working, this is likely a regression which we didn't catch because there's no way to automatically test this (yet)
  • Main process crashes might not be generated if the Crash Reports/pending folder doesn't exist (this mostly happens with local builds)
  • Main process crashes might not be generated if the InstallTime<buildid> file is not present
  • Always provide a value for the installation time, even when we fail to read it from the corresponding file
  • Parse the parent PID correctly
  • Create the pending folder if it's missing
Assignee: nobody → gsvelto
Status: NEW → ASSIGNED

The severity field is not set for this bug.
:gsvelto, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(gsvelto)
Severity: -- → S3
Flags: needinfo?(gsvelto)
Pushed by gsvelto@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fbd46c7fb4d1 Make the WER interceptor more robust r=yjuglaret

Comment on attachment 9373044 [details]
Bug 1874235 - Make the WER interceptor more robust r=yjuglaret

Beta/Release Uplift Approval Request

  • User impact if declined: N/A
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce: N/A
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky):
  • String changes made/needed: None
  • Is Android affected?: No
Attachment #9373044 - Flags: approval-mozilla-beta?

Comment on attachment 9373044 [details]
Bug 1874235 - Make the WER interceptor more robust r=yjuglaret

Approved for 124.0b4

Attachment #9373044 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Target Milestone: --- → 125 Branch
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
  • Always provide a value for the installation time, even when we fail to read it from the corresponding file
  • Parse the parent PID correctly
  • Create the pending folder if it's missing

Original Revision: https://phabricator.services.mozilla.com/D198699

Attachment #9387834 - Flags: approval-mozilla-esr115?

Comment on attachment 9387834 [details]
Bug 1874235 - Make the WER interceptor more robust

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: Required for the uplift of bug 1872920
  • User impact if declined: See bug 1872920
  • Fix Landed on Version: 125
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): The patch affects code that only runs after Firefox crashed, the risk of regression is minimal
Attachment #9387834 - Flags: approval-mozilla-esr115? → approval-mozilla-esr115+
Regressions: 1893408
See Also: → 1893406
Regressions: 1893406
See Also: 1893406
See Also: → 1816848
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: