Closed
Bug 1874235
Opened 1 year ago
Closed 1 year ago
Windows Error Reporting can fail in several ways
Categories
(Toolkit :: Crash Reporting, defect)
Toolkit
Crash Reporting
Tracking
()
RESOLVED
FIXED
125 Branch
People
(Reporter: gsvelto, Assigned: gsvelto)
References
Details
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr115+
|
Details | Review |
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
Assignee | ||
Comment 1•1 year ago
|
||
- 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
Updated•1 year ago
|
Assignee: nobody → gsvelto
Status: NEW → ASSIGNED
Comment 2•1 year ago
|
||
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)
Assignee | ||
Updated•1 year ago
|
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 4•1 year ago
|
||
Comment 5•1 year ago
|
||
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 6•1 year ago
|
||
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+
Updated•1 year ago
|
Updated•1 year ago
|
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•1 year ago
|
||
- 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
Updated•1 year ago
|
Attachment #9387834 -
Flags: approval-mozilla-esr115?
Assignee | ||
Comment 9•1 year ago
|
||
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
Updated•1 year ago
|
Attachment #9387834 -
Flags: approval-mozilla-esr115? → approval-mozilla-esr115+
Updated•1 year ago
|
status-firefox-esr115:
--- → fixed
Comment 10•1 year ago
|
||
uplift |
Updated•10 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•