116
edits
Chrishofmann (talk | contribs) No edit summary |
Chrishofmann (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
What data do we have? | |||
== How Can We Use It To Get to the Bottom of Crash Problems == | |||
QA activities -- who, what, when, where, and how: | |||
* getting to a reproducible environment/test case | |||
** identifying a common config | |||
*** OS version, hardware & driver correlations | |||
*** addon/plugin correlations | |||
*** graphics cards and driver correlations | |||
*** urls, domains, locales/regions of sites visited | |||
*** common user actions in comments | |||
**** e-mailing some some users?... (new automated system coming on-line) | |||
*** calibrating which Product Releases where the crash is seen. | |||
* Time & Regression Ranges -- looking at the various forms of time data: | |||
** Finding Spikes and Volume Regressions | |||
*** time of crash (breakpad/socorro dup reports) https://bugzilla.mozilla.org/show_bug.cgi?id=579136 | |||
*** time since last crash | |||
*** time since start up (uptime) | |||
*** time of the build | |||
*** install time | |||
* Connecting to External and Other Events | |||
** Plugin/Addon Releases | |||
** Web Site Changes | |||
** Firefox/Gecko Source Code Changes | |||
** Build Environment Changes... new compliers, build configs. | |||
* With a reproducible test case... | |||
** reduced test case | |||
** crash recorded on VM... | |||
* developer investigations | |||
** finding problems though source inspection | |||
*** using regression ranges to examine change sets | |||
** Running Minidupms in the debugger. | |||
== What data do we have? == | |||
<pre> | <pre> | ||
| Line 39: | Line 78: | ||
</pre> | </pre> | ||
== Beyond http://crash-stats.mozilla.com/ == | |||
Beyond http://crash-stats.mozilla.com/ | |||
http://people.mozilla.com/crash_analysis/20101213/ | === http://people.mozilla.com/crash_analysis/20101213/ === | ||
20101213-pub-crashdata.csv.gz | 20101213-pub-crashdata.csv.gz summary of all the reports for a given day | ||
20101213_Firefox_3.6.9-core-counts.txt -- for finding threading issues | 20101213_Firefox_3.6.9-core-counts.txt -- for finding threading issues | ||
20101213_Firefox_3.6.9-interesting-addons-with-versions.txt | 20101213_Firefox_3.6.9-interesting-addons-with-versions.txt | ||
20101213_Firefox_3.6.9-interesting-modules-with-versions.txt.gz | 20101213_Firefox_3.6.9-interesting-modules-with-versions.txt.gz | ||
http://people.mozilla.com/~jst/new-crashes/Firefox/latest/ | === http://people.mozilla.com/~jst/new-crashes/Firefox/latest/ === | ||
whats new? finding crashes when they are introduced helps fix them easier and faster | whats new? finding crashes when they are introduced helps fix them easier and faster | ||
http://people.mozilla.com/~chofmann/crash-stats/20101213/ | === http://people.mozilla.com/~chofmann/crash-stats/20101213/ === | ||
top-4.0b8pre.html ( just the firefox crashes... ) | top-4.0b8pre.html ( just the firefox crashes... ) | ||
| Line 97: | Line 98: | ||
mozilla-central-crash-trend.csv (which mozilla-central builds are most crashy?) | mozilla-central-crash-trend.csv (which mozilla-central builds are most crashy?) | ||
http://people.mozilla.com/crash_stacks/ | === http://people.mozilla.com/crash_stacks/ === | ||
beyond just a signature | beyond just a signature | ||
edits