CrashKill/2012-10-01

From MozillaWiki
Jump to: navigation, search

General

  • Blog - got the go-ahead to move forward with a blog
  • Sheila will check with PR/Marketing on naming
  • File bugs to get it setup
  • Marcia noted - check who can have access - everybody on the mailing list
  • Sheila will report back next week
  • Plan for tracking crashes/releases
    • Alex etherpad - next action is for Marcia to update pages/queries for desktop
    • Then we can talk about responsibilities and

Desktop

  • Super top crash
    • High crash rate on trunk - Win64 bit specific - related to PGO updates
    • We disabled PGO updates for the Win64 build - waiting for people to update
    • Should start going down
    • No current test on trunk and aurora on automation that tests whether or not a build starts up. Not doing this for Win64 bit.
    • Talk to Asa about why we don't support this.
  • Marcia will scan the list of trunk bugs
  • Kairo - trunk looks ok (ignoring the top crash)
  • Some new landings to watch in the next week.
  • Trunk
    • Couple of new crashes
  • Beta
    • New Flash bug - showed up in explosive report
    • Marcia will cc Adobe people on the bug
    • Top 10 crashes on B5 are hangs
    • Ben's hang code only on trunk
    • Marcia - beta seems to look worse for hangs
    • Sheila - talk to Ben about what we are doing with the data
  • Aurora
    • Need to check crash list

Mobile

  • Trunk
    • Naoki - still lots of startup crashes on Nightly
    • Many nightly fixes in the queue so we should see that go down
  • Haven't had time to check into Aurora/Beta yet
  • Naoki - beta is showing almost the same as the current release - hoping this correlates to lower crash rate on release.
  • Chris - any new information on crashes on custom kernals? Naoki - getting some signatures. bug 790139
    • Trying to fix the ones that are most crashy
    • Suddenly had a huge spike of these types of crashes
    • Need a report to show crashes per OS - Naoki spoke to Laura/Kairo about this. Kairo, we don't have the data in the crash reports to easily tell them apart.
  • Kairo - daily crashes per user page on Socorro. Don't get all the numbers on Nightly right now.
    • Top crashes in front page is ok
    • Crashes per user numbers are not quite right - bug 795349

B2G

  • Naoki - looked today
    • Showing 2 crashes from the device so we are getting them but they aren't workable because we don't have symbols.
    • Need the releng to the build generation.
    • When will we have this in place? Need to talk to releng.
    • Not a blocker for actual dogfooding but we cannot start on stability.
  • We had a meeting to finalize the UX flow for crashes - implementation has not started.
  • Content crashes has not been implemented yet.