99
edits
No edit summary |
(→Ideas from Jesse Ruderman: grouping crash stacks suggestion) |
||
Line 5: | Line 5: | ||
* Organize the top 50 crashes by component (layout, networking, javascript engine, etc), guessing based on the directory the source file is in. | * Organize the top 50 crashes by component (layout, networking, javascript engine, etc), guessing based on the directory the source file is in. | ||
** Are you able to group crashes from different builds? In the trivial case, one can group crashes within one build, but if one symbolicates the stack and use regex matching, one can group crashes that have occurred in different builds. Is this being done now? - [mailto:rkiddy@mozilla.com ray] | |||
* Let me see a topcrash report for crashes in a given component. | * Let me see a topcrash report for crashes in a given component. | ||
* In tables, use background colors (saturation or brightness) so that large numbers stand out. A table cell containing the number 91 might be darker than a table cell containing the number 19, for example. | * In tables, use background colors (saturation or brightness) so that large numbers stand out. A table cell containing the number 91 might be darker than a table cell containing the number 19, for example. |
edits