Closed Bug 1727149 Opened 3 years ago Closed 3 years ago

undo IPCError-browser | ShutDownKill improvement

Categories

(Socorro :: Signature, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

Details

Attachments

(1 file)

In bug #1612569, we changed signature generation to include the original signature for IPCError-browser | ShutDownKill signatures so we could differentiate between them.

This overwhelmed TopCrashers reports with a multitude of shutdown signatures.

We're not really looking at these, so for now, let's undo that change so the shutdown signatures all go in the same bucket again.

I can work on this after the codefreeze is lifted in September.

Assignee: nobody → willkg
Status: NEW → ASSIGNED

I pushed this in bug #1731787. Marking as FIXED.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #0)

In bug #1612569, we changed signature generation to include the original signature for IPCError-browser | ShutDownKill signatures so we could differentiate between them.

This overwhelmed TopCrashers reports with a multitude of shutdown signatures.

Is there a way to query this / aggregate on those on crash-stats? In case someone wanted to look at them...

Flags: needinfo?(willkg)

I didn't reprocess crash reports, so crash reports that had their signatures computed before the change still have them. You can aggregate on a date range ending with 2021-09-21.

Flags: needinfo?(willkg)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: