Table of Contents CSI:Mozilla The following slides are available in this presentation: CSI:Mozilla - Crash Scene Investigations Robert Kaiser, "KaiRo" <kairo@kairo.at> Mozilla Crash Scene Investigator Slides: http://slides.kairo.at/fosdem2012/ Created for Mozilla Developer Room at FOSDEM 2012 in Brussels. Written in HTML 5 with CSS 3 and JavaScript. Navigation via links on all slides, via access keys (e.g. "n"/Alt+Shift+N for "next") or back/forward arrow keys Contents 01/2012 Robert Kaiser & the Mozilla CrashKill team CrashKill Mission: To improve stability of our products Stability Factors Reading The Tea Leaves Trends: crash rates, "explosiveness" Topcrash lists, crash ranks Correlations with code, website, 3rd-party software changes Specifics (browser vs. plugin, OSes, uptime, etc.) Pitfalls: rates and ADUs, ranks, signature changes Areas of Focus Long tail 3rd-party issues, hangs, malware Analysis by component Startup crashes Mobile: fewer users, devices, Java, Android Symbol Sender Most crashes in core, not desktop/mobile-specific Socorro crash-stats.mozilla.com Working closely with Socorro team to identify and prioritize front-end features that will help us diagnose crashes Bugzilla Best Practice Add crash keyword If a regression, add regression keyword Add regressionwindow-wanted keyword Try finding regression window Try to correlate with push log If possible, find and add steps to reproduce Need crashing websites for work: add needURLs keyword Community Keep community engaged by fixing their issues Community member Scoobidiver: >650 crash bugs filed We need more members of the community contributing in a more coordinated fashion From filing good bugs via regression hunting to trying to fix YOU can help! How You Can Help Make sure you submit crash reports, ideally including email and comment Report bugs for crashes, tell us if you can reproduce them If you have a regular Firefox crash, help us to diagnose it - email marcia@mozilla.com with details Visit us in #crashkill on irc.mozilla.org CrashKill meetings - Mondays @ 10am Pacific ("7pm Central Europe") x290 Try fixing crashes - each one counts! The CrashKill-Team
CSI:Mozilla - Crash Scene Investigations Robert Kaiser, "KaiRo" <kairo@kairo.at> Mozilla Crash Scene Investigator Slides: http://slides.kairo.at/fosdem2012/ Created for Mozilla Developer Room at FOSDEM 2012 in Brussels. Written in HTML 5 with CSS 3 and JavaScript. Navigation via links on all slides, via access keys (e.g. "n"/Alt+Shift+N for "next") or back/forward arrow keys Contents 01/2012 Robert Kaiser & the Mozilla CrashKill team
CrashKill Mission: To improve stability of our products Stability Factors Reading The Tea Leaves Trends: crash rates, "explosiveness" Topcrash lists, crash ranks Correlations with code, website, 3rd-party software changes Specifics (browser vs. plugin, OSes, uptime, etc.) Pitfalls: rates and ADUs, ranks, signature changes Areas of Focus Long tail 3rd-party issues, hangs, malware Analysis by component Startup crashes Mobile: fewer users, devices, Java, Android Symbol Sender Most crashes in core, not desktop/mobile-specific Socorro crash-stats.mozilla.com Working closely with Socorro team to identify and prioritize front-end features that will help us diagnose crashes Bugzilla Best Practice Add crash keyword If a regression, add regression keyword Add regressionwindow-wanted keyword Try finding regression window Try to correlate with push log If possible, find and add steps to reproduce Need crashing websites for work: add needURLs keyword Community Keep community engaged by fixing their issues Community member Scoobidiver: >650 crash bugs filed We need more members of the community contributing in a more coordinated fashion From filing good bugs via regression hunting to trying to fix YOU can help! How You Can Help Make sure you submit crash reports, ideally including email and comment Report bugs for crashes, tell us if you can reproduce them If you have a regular Firefox crash, help us to diagnose it - email marcia@mozilla.com with details Visit us in #crashkill on irc.mozilla.org CrashKill meetings - Mondays @ 10am Pacific ("7pm Central Europe") x290 Try fixing crashes - each one counts! The CrashKill-Team
Reading The Tea Leaves Trends: crash rates, "explosiveness" Topcrash lists, crash ranks Correlations with code, website, 3rd-party software changes Specifics (browser vs. plugin, OSes, uptime, etc.) Pitfalls: rates and ADUs, ranks, signature changes
Areas of Focus Long tail 3rd-party issues, hangs, malware Analysis by component Startup crashes Mobile: fewer users, devices, Java, Android Symbol Sender Most crashes in core, not desktop/mobile-specific
Socorro crash-stats.mozilla.com Working closely with Socorro team to identify and prioritize front-end features that will help us diagnose crashes
Bugzilla Best Practice Add crash keyword If a regression, add regression keyword Add regressionwindow-wanted keyword Try finding regression window Try to correlate with push log If possible, find and add steps to reproduce Need crashing websites for work: add needURLs keyword
Community Keep community engaged by fixing their issues Community member Scoobidiver: >650 crash bugs filed We need more members of the community contributing in a more coordinated fashion From filing good bugs via regression hunting to trying to fix YOU can help!
How You Can Help Make sure you submit crash reports, ideally including email and comment Report bugs for crashes, tell us if you can reproduce them If you have a regular Firefox crash, help us to diagnose it - email marcia@mozilla.com with details Visit us in #crashkill on irc.mozilla.org CrashKill meetings - Mondays @ 10am Pacific ("7pm Central Europe") x290 Try fixing crashes - each one counts!