I would like to request a new feature: stack trace analysis. Scenario: you have a set of crashes all having a common frame (e.g. fastcopy_I - https://crash-stats.mozilla.com/report/list?query_search=signature&query_type=contains&reason_type=contains&range_value=4&range_unit=weeks&hang_type=any&process_type=any&signature=fastcopy_I). However, the stacks of the crashes don't follow a common pattern. You should be able to run a report (probably against a specific set of crashes) and glean useful information about the stacks - frame counts and frequencies, similarity between common stacks, etc. From this report, hopefully a few items stick out, allowing you to narrow your bug squashing effort. The talk on #metrics and #breakpad that prompted this bug seemed to indicate a multi-phase implementation which is first implemented as a MR job and eventually makes its way to the crash-stats UI. I don't know enough about the systems to be more specific than that.
Closing old issues. Not in current scope of work.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.