66
edits
CrashKill/Topcrash: Difference between revisions
Update the criteria to add a default minimum crashes and installations
(Remove Android Intel from the top crash list, https://github.com/mozilla/relman-auto-nag/issues/1780#issuecomment-1323051694) |
(Update the criteria to add a default minimum crashes and installations) |
||
| Line 17: | Line 17: | ||
** Top 5 socket and utility process crashes on Beta and Release but only if they affect 5+ installations. | ** Top 5 socket and utility process crashes on Beta and Release but only if they affect 5+ installations. | ||
** Top 5 desktop browser crashes on Linux-, Mac-, and Win10- specific list on Beta and Release | ** Top 5 desktop browser crashes on Linux-, Mac-, and Win10- specific list on Beta and Release | ||
*** If volume is very similar to the top 5, other bugs might still be included. | *** If volume is very similar to the top 5, other bugs might still be included. | ||
*** High volume Win7- and Win8- crashes should also be considered if they affect a significant number of users. | *** High volume Win7- and Win8- crashes should also be considered if they affect a significant number of users. | ||
| Line 38: | 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 only 2 or 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`) | ||