Firefox Core Engineering/Get More Data Faster

This effort is establish a shorter path between client crashes and actionable data.

Step 1

1. Land content crash ping (enables new crash ping types)​.​ [end of Q4 2016] completed: 1293656
2. Determine how to report on unsymbolicated stack in crash pings (we want to identify what we can answer from the data we collect now, without aggregating and without symbolicating)​.​ [mid-January 2017]
3. Scale/load test the new symbolapi.m.o (we want to know if this will serve its current function AND a future function for release users)​. [mid-January 2017] This has been abandoned in favor of a rewrite led by peterbe.
4. Determine if we can include frame pointers on release (because it enables future steps). [end of Q4 2016]​ completed: 1322735

Step 2

1. Land the pingSender (so we can send a crash ping as soon as possible)​. [mid-January 2017] completed​: 1310703
2. Symbolicate crash ping stacks via batch in data processing. --together with--
3. Create "client-side" signatures from symbolicated stacks via batch in data processing.​ in progress: 1357431

Step 3

1. Implement clustering of crashes on the client-side, based on signatures. [TBD]
2. Establish means of identifying top crashers in client-side data via signatures. [TBD]
3. Enable correlating between client-side crash clusters and crash-stats-side crash clusters, via client crash id (see 1322611). [TBD]

Step 4

1. Symbolicate crash ping stacks on the client, via https://symbolserver.mozilla.org/symbolicate (see peterbe). [TBD]
2. Return signatures to the client, via a signature service. [TBD]

Step 5

1. Introduce new crash ping types beyond Main and Content (GPU (1297843 and 1352496), webextension, etc). [TBD]