CrashKill/2013-01-14

From MozillaWiki
Jump to: navigation, search

General

The "Are We Stable Yet?" dashboard now has better crash rate numbers after a fix in Socorro (bug 826100).

Socorro

Flash

  • bug 829987 - missing symbols for MS DLLs - This has an impact on Flash hangs, many of which now show up as hang@kernelbase.dll@...
  • bug 830393 - crash in F1186119096 - new significant regression in latest Flash beta (11.6.602.137)
  • 11.5 regression bug 810797 is fixed in that newest beta, though, apparently. It looks like the other one, bug 807714, is also gone.
  • 11.6 regressions bug 822003 and bug 820836 are unchanged, bug 822005 seems to be lower.

Desktop

Beta

  • Crash rate is somewhat high, bug 806820 plays a major part, just like in release (see there)

Aurora

Release

  • Tremendous uptake, 60M ADI yesterday (on a Sunday!). General crash rate slightly on the high side compared to 17.0.1 with similar uptake.
  • bug 806820 - Facebook-related, SuppressDeletedPropertyHelper
    • Now #2 topcrash (yesterday), 10+% of all 18.0 crashes, possible that some of #1 topcrash "empty dump" signature can be attributed to this as well (though it's hard to be sure).
    • Rise in last days could be because of more general-population Facebook-using people adopting 18, or because more people are using FB on weekends.
  • bug 783369 - Norton Confidential 2012/2013 (couictlr.dll, coffplgn.dll)
    • Stable over the last few days, #3 topcrash yesterday, a bit over 10%, vast majority is 2012 version.
    • Norton is rolling out an update to 2013 with a fix soon. They are also looking into a possible update for 2012.
  • bug 801394 - nsInputStreamPump::OnInputStreamReady, with randomly named DLL (malware)
    • Alex has reached out to AV vendors, we've been working with users to identify the DLL(s) affected - there seem to be at least two variants.
    • Dropped significantly in yesterday's data, (AV software catching up?), now #4 topcrash in yesterday's 18 data with roughly 4% of all crashes.
    • Even though Honza mentioned in comment #18 that this may still be a Firefox bug in the end, we seem to dodge that bullet now.

Trunk

Mobile

B2G

Notes