CrashKill/Firefox4: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
==General Agenda==
==General Mandate==


* To resurrect the Crashkill effort targeted specifically at the 2.0 release. We meet weekly to triage bugs and discuss issues.
* Monitor and track the stability metrics specifically focused on the Firefox 4 release.
* We would like to focus the developers' efforts on addressing the most serious crashers particularly regressions.
* Focus people's attention on addressing the most serious crashers particularly regressions.
* We will also be monitoring crash trends and reporting on general stability.
* Ensure that new crash regressions are logged.
* We will use the keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
* Monitoring crash trends and regular reports on general stability to the team.
* We will make sure the module owner is cc'd on the bug so they can be assigned appropriately.
* Consistent use of keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
* Communicating status to the development team and others on the stability of the app.
* Ensure module owners are cc'd on the bugs so they can be assigned appropriately.
* Old Crashkill notes and info can be found at https://wiki.mozilla.org/CrashKill.


==Latest Stability Data==
==Latest Stability Data (03/03/11)==


* Beta9 - 2.35 crashes per 100 ADU with 1,200,757 users.
* Beta12 - 2.33 crashes per 100 ADUs with 2 million users.
* Beta8 (comparable) - 2.26 crashes per 100 ADU with 1,211,936 users.
* Trunk - 1.92 crashes per 100 ADUs with 61K users.
* Trunk - Low volume of users ~15K users. Looking at new regressions.


==Status==
==Status==


(Updated Jan 19th, 2011)
(Updated Mar 3, 2011)


We are now in the final stages of the release so monitoring for stability regressions is key. A few things we are tracking closely....
We are now in the very final stages of the release so monitoring for stability regressions is key.  


===Crash Regressions From 3.6.13===
===Crash Regressions From 3.6.13===


Many of the top 30 browser crashes are new in 3.6.13. Here is a complete list along with current status.
Many of the top 30 browser crashes are regressions from 3.6. Here is a complete list.


* [https://bugzilla.mozilla.org/show_bug.cgi?id=595351 Bug 595351] - js::mjit::EnterMethodJIT crash. We didn't think we could do much about this but we now have additional data that might help us track down the problem. Someone is working on it. Currently a softblocker.
* http://people.mozilla.com/~chofmann/crash-stats/20110228/compare-rank-4.0b13pre-4.0b12-3.6.14.txt
* [https://bugzilla.mozilla.org/show_bug.cgi?id=630191 Bug 630191] - #4 on Beta10 but lower on the trunk. Hardblocker, Final.
 
* [https://bugzilla.mozilla.org/show_bug.cgi?id=630193 Bug 630193] - #6 on Beta10 but not registering on the trunk. Fixed - Beta12.
===Browser Crashes==
* [https://bugzilla.mozilla.org/show_bug.cgi?id=626343 Bug 626343] - Hardblocker, Final+.
 
* [https://bugzilla.mozilla.org/show_bug.cgi?id=500105 Bug 500105] - Not a blocker since can't repro and don't know the cause.
Top browser crashes for Beta12
* [https://bugzilla.mozilla.org/show_bug.cgi?id=615098 Bug 615098] - Softblocker, Final+.
 
* [https://bugzilla.mozilla.org/show_bug.cgi?id=612098 Bug 612098] - Can be closed once [https://bugzilla.mozilla.org/show_bug.cgi?id=615475 Bug 615475] is fixed.
* http://people.mozilla.com/~chofmann/crash-stats/20110228/top-4.0b12.html
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=629046 Bug 629046] - Significantly reduced in volume, probably related to another fix.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=602225 Bug 602225] - @ js::gc::MarkObject. Not a blocker, still needs to be looked at.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=601102 Bug 601102] - Not a blocker, still needs some review.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=591513 Bug 591513] - Crash in older Betas, moved up in Beta9. Untriaged
* [https://bugzilla.mozilla.org/show_bug.cgi?id=630427 Bug 630427] - Untriaged


===Plugin Crashes===
===Plugin Crashes===
Top plugin crashes for Beta12
* http://people.mozilla.com/~chofmann/crash-stats/20110228/top-plugin-crashes-40b12.html
   
   
(Marcia to help fill in stuff we want to monitor with plugins)


* [https://bugzilla.mozilla.org/show_bug.cgi?id=572134 Bug 572134] - This is the biggy that got fixed. Waiting for Beta10 to see impact on users. This should noticably reduce the Flash crashes.
===Trunk Regressions===
** Crash data reviews shows a correlation to Adblock Plus with these crashes, although it was reproducible without AP.
 
* [https://bugzilla.mozilla.org/show_bug.cgi?id=585913 Bug 585913] - This was a problem introduced with the Flash release on Nov 3rd. We are working with Adobe to get this fixed but no timeline on that.
Top trunk browser crashes


===Trunk Regressions===
* http://people.mozilla.com/~chofmann/crash-stats/20110228/top-4.0b13pre.html


These were the ones appearing on the top 20 list.
Top trunk plugin crashes


* [https://bugzilla.mozilla.org/show_bug.cgi?id=625330 Bug 625330] - Win64
* [https://bugzilla.mozilla.org/show_bug.cgi?id=613716 Bug 613716] - Win64
* [https://bugzilla.mozilla.org/show_bug.cgi?id=626599 Bug 626599] - fixed in Tracemonkey
* [https://bugzilla.mozilla.org/show_bug.cgi?id=625753 Bug 625753] - Might depend on [https://bugzilla.mozilla.org/show_bug.cgi?id=625315 Bug 625315] which is not a blocker.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=625247 Bug 625247] - Fixed
* [https://bugzilla.mozilla.org/show_bug.cgi?id=626841 Bug 626841] - Fixed


==Bug Lists==
==Bug Lists==
Line 84: Line 74:


*Dial-in for the meeting is x290
*Dial-in for the meeting is x290
*The Meeting is now every! Tuesday at 12:30AM till 1PM Pacific
*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)
*650-903-0800 or 650-215-1282 x92 Conf# 290 (US/INTL)
*1-800-707-2533 (pin 369) Conf# 290 (US)
*1-800-707-2533 (pin 369) Conf# 290 (US)
*MV - Meet in Zombocom Conference Room on Floor 3.
*MV - Meet in Zombocom Conference Room on Floor 3.
*Backchannel on irc.mozilla.org is #planning
*Backchannel on irc.mozilla.org is #crashkill
 
==Meeting Notes==

Revision as of 19:00, 3 March 2011

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.

=Browser Crashes

Top browser crashes for Beta12

Plugin Crashes

Top plugin crashes for Beta12


Trunk Regressions

Top trunk browser crashes

Top trunk plugin crashes


Bug Lists

A bunch of queries we like to refer to.

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
Retrieved from "https://wiki.mozilla.org/index.php?title=CrashKill/Firefox4&oldid=288564"