CrashKill/Firefox4

General Mandate

• Monitor and track the stability metrics specifically focused on the Firefox 4 release.
• Focus people's attention on addressing the most serious crashers particularly regressions.
• Ensure that new crash regressions are logged.
• Monitoring crash trends and regular reports on general stability to the team.
• Consistent use of keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
• Ensure module owners are cc'd on the bugs so they can be assigned appropriately.

Latest Stability Data (03/03/11)

• Beta12 - 2.33 crashes per 100 ADUs with 2 million users.
• Trunk - 1.92 crashes per 100 ADUs with 61K users.

Status

(Updated Mar 3, 2011)

We are now in the very final stages of the release so monitoring for stability regressions is key.

Crash Regressions From 3.6.13

Many of the top 30 browser crashes are regressions from 3.6. Here is a complete list.

• http://people.mozilla.com/~chofmann/crash-stats/20110228/compare-rank-4.0b13pre-4.0b12-3.6.14.txt

=Browser Crashes

Top browser crashes for Beta12

• http://people.mozilla.com/~chofmann/crash-stats/20110228/top-4.0b12.html

Plugin Crashes

Top plugin crashes for Beta12

• http://people.mozilla.com/~chofmann/crash-stats/20110228/top-plugin-crashes-40b12.html

Trunk Regressions

Top trunk browser crashes

• http://people.mozilla.com/~chofmann/crash-stats/20110228/top-4.0b13pre.html

Top trunk plugin crashes

Bug Lists

A bunch of queries we like to refer to.

• Top crashes - (keyword=topcrash and blocking 2.0=beta, final)
  • All top crashers
  • Top crashers - nominated
  • Top crashers - reproducible
  • Top crashers - needs info
  • Top crashers - regressions
  • Top crashes - not modified since 2010-09-01
  • Top crashers - fixed (so we can go back verify in the next beta).
  • Unassigned (nobody@mozilla.org, general@js.bugs)

• All crashes - (keyword=crash, topcrash and blocking 2.0=beta, final)
  • All crashes
  • All crashes nominated
  • All crashes - fixed
  • All crashes - not modified since 2010-09-01

Analysis

http://crash-stats.mozilla.com/products/Firefox

Meeting Logistics

• Dial-in for the meeting is x290
• The Meeting is now every Monday at 10:30AM till 11:00am Pacific
• 650-903-0800 or 650-215-1282 x92 Conf# 290 (US/INTL)
• 1-800-707-2533 (pin 369) Conf# 290 (US)
• MV - Meet in Zombocom Conference Room on Floor 3.
• Backchannel on irc.mozilla.org is #crashkill