66
edits
CrashKill/Topcrash: Difference between revisions
Correct the minimum installations threshold
(Update the criteria to add a default minimum crashes and installations) |
(Correct the minimum installations threshold) |
||
| Line 37: | Line 37: | ||
* Each release channel (i.e., Release, Beta, Nightly) should be considered separately. Combining crash reports from multiple channels, e.g., beta and release might hide beta-only top-crashes. | * Each release channel (i.e., Release, Beta, Nightly) should be considered separately. Combining crash reports from multiple channels, e.g., beta and release might hide beta-only top-crashes. | ||
* If there's less than 15 crashes per week on a signature, that bug probably still doesn't qualify - same for crashes happening to | * If there's less than 15 crashes per week on a signature, that bug probably still doesn't qualify - same for crashes happening to less than 3 installations. | ||
* Crash signatures that should not be automatically considered top crashers even if high volume: | * Crash signatures that should not be automatically considered top crashers even if high volume: | ||
** All signatures starting with `EMPTY: ` or `OOM | large | EMPTY: ` (examples: `EMPTY: no crashing thread identified; HeaderMismatch` and `OOM | large | EMPTY: no crashing thread identified; StreamSizeMismatch`) | ** All signatures starting with `EMPTY: ` or `OOM | large | EMPTY: ` (examples: `EMPTY: no crashing thread identified; HeaderMismatch` and `OOM | large | EMPTY: no crashing thread identified; StreamSizeMismatch`) | ||