Stop sending orphaned crash reports
Categories
(Toolkit :: Crash Reporting, defect, P2)
Tracking
()
People
(Reporter: calixte, Assigned: gsvelto)
Details
Attachments
(2 files)
In crash-stop (see screenshot from bug 1631234), it's quite confusing.
The buildids are probably incorrect:
https://bugzilla.mozilla.org/show_bug.cgi?id=1631232#c16
According to :pascalc, we've such crashes from January 2020.
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:gsvelto, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 2•5 years ago
|
||
Sorry I forgot about this. These are orphaned crashes, i.e. crashes for which we have a .dmp file but no .extra file. They used to be a significant problem so I added code to submit them with synthesized metadata. Since we don't know in which version of Firefox they happened the install time field - and many others - is empty. I should have fixed most of the issues that caused them so now there's a very small number and I don't think we care anymore because they should also go a way once I'm done with OOP crash generation. Let's change this bug to disable this behavior and just clean them up.
I'm changing the title accordingly.
Comment 3•5 years ago
|
||
The severity field is not set for this bug.
:gsvelto, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
|
||
S1 or S2 bugs need an assignee - could you find someone for this bug?
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
We originally added this functionality in bug 1566855 because we were
seeing a significant amount of orphaned crashes not being submitted.
Notably some of these were early content process startup crashes and
missing them made us unaware of severe issues that would affect our
users. In the meantime we've addressed most of the cases where a crash
would be orphaned. Since the crashes submitted this way have a buildid
that does not match the version of Firefox that actually crashed they
can be confusing during crash triage.
Given the above we can safely remove this functionality. This patch
reverts most of the changes from bug 1566855 but leaves the test
refactorings in place.
Comment 7•5 years ago
|
||
bugherder |
Comment 8•5 years ago
|
||
The patch landed in nightly and beta is affected.
:gsvelto, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•5 years ago
|
Description
•