CrashKill/2012-11-19

General

Any New/spiked Windows 8 crashes after the latest release
- bug 813092 Firefox startup crash in VirtualAllocStub
Stability feedback on Thursday/Fri - most US team members will be off those two days
- marcia traveling all day Friday so will not be watching anything closely
- KaiRo will be watching things over that period - marcia will look at some stuff on Thursday
Holiday coverage in December
- https://docs.google.com/spreadsheet/ccc?key=0Ait_RA8Il0WWdFhxT2NBQXRBdm5NaWJOWFllOE5uS0E#gid=0 - Mobile and B2G still have ?

In preparation of bsmedberg's hang reporting rework (the product side is in 18 and coming to beta this week), Socorro is now not recording the browser sides of hang reports since Thursday. Therefore they are fading out of the topcrash reports and we need to adjust the criteria for setting the topcrash keyword.

Flash 11.5 crashes
- bug 810797 and bug 807714 continue to rise as they're new regressions with 11.5 and this release is being picked up more and more.
bug 813205 crash in F21225463

https://bugzilla.mozilla.org/show_bug.cgi?id=812307#c12 (datamngr) - Crash has risen and was on the explosive report this weekend.
bug 770238 (Yandex Bar) - this one also has been rising into the topcrash ranges.
bug 812683 IE 10 Preview crash

Those are not out of control but cause for some concern, but they're 3rd-party issues we might not be able to solve on our side.

bug 812985 crash in _cairo_d2d_create_brush_for_pattern
- Core|Graphics regression that also affects trunk

bug 812203 - spiked on the 15th, but is now fixed
bug 813024 - Mac crash which is referenced as top crash by Scoobidiver, but has a lot of dupes - likely the same person crashing
bug 812636 - Web RTC crash which might be a dupe

Today's explosive report for reference: https://crash-analysis.mozilla.com/rkaiser/2012-11-18/2012-11-18.firefox.19.explosiveness.html
The not yet tracked topcrashers are mostly Win64, which isn't tier-1 and we don't have on Aurora anyhow.

Crash rates for beta are up in 17.0b7 compared to other betas before, not because of new crashes but because crash reporting on Android 4.2 works again. Level in the same ballpark now as 16 had on beta.
We have some JB-only crashes, now happening mostly with 4.2 and Nexus 7, that we'll need to push for in the 18 beta timeframe.
bug 775142 is the topcrash on 18 and 19, apparently we are confusing localizers and crashing with their strings.

We need more testing of the crash reporting flow.
Biggest blocker atm is bug 811341 - we need to send reports when we're already online!
We need testing around bug 811778 to make sure we follow the spec correctly.
- We don't have crashmenow for B2G so it makes it a bit more difficult
  - There is a way to kill in ADB - that should generate a crash.