Breakpad/Status Meetings/2008-Apr-9

From MozillaWiki
Jump to: navigation, search

Key topic - what it takes to make fx3 beta5 and final more stable.

 Meeting details:
* 2:00p PDT, 5:00p EDT 
* 650-903-0800 or 650-215-1282 x91 conf# 249 (US/Intl)
* 1-800-707-2533 (pin 369) conf# 249 (US)
* #breakpad for backchannel

Project Update

  • pushes from last week
    • processor summary
      • refactored -- better job management, queue status
      • changed mutual exclusion method
      • ability to flag for priority processing
      • still have a 5 minute delay between submission and queue entry, currently working on it
    • reporter summary
      • added ability to priority-flag a submitted report
      • working on implementation of aggregate and summary tables for end April
  • tentative schedule
    • 0.5 by end April
    • 0.6 by mid May

Action items from last week

  • Ted to look at feasability of keeping minidumps for topcrashes
  • Ted to investigate aggregate URL reports
  • chofmann to get kkovash to look at MTBF calculations, regression analysis
  • chofmann filed to break out the idea of creating an analysis report to spot problematic .dll's in the process list
  • ss to add Firefox 3.0b5 to query form as soon as we start getting beta5 builds.
  • ss or chofmann - get blocklisting requests on file for the rest of crashing extensions and plugins in b4

Progress on Top Crash Analysis -- Beta 4.

  • Sam's wiki page for summarizing status of the analysis work on each release is also working fairly well - See:
  • This can serve as a work around until we get solutions for bugs 448156, 411357
  • Many of the top crashes for Beta 4 have to do with Extension/Plugin compatibility, and corruption with installation setup. need to make sure blocklisting requests are tracking where we need them

Crash Analysis Needs

  • most of the rest of these involve setting up a controlled access server to protect sensitive data like e-mail address and browsing history, or contents of memory when crashes occurred. (That is Bug 411419 – Add way to hide confidential crash reports) -- if we do something based on only sites that are listed the alexa top 100/500 (ala ) then that might be a report that we could publish publicly .

Release Comparison Analysis

  • For overall release metrics that can help us compare releases we need to get some total crash numbers and MTBF calcs and reporting in place.
    • Talked to Ken this week to provide some background and get him involved in creating some MTBF numbers and help in validating these "release metrics"
    • Morgamic is also thinking about the best way to do these non-dyamic query reports that give us a sapshot of overall release metrics every day or hour.

Sorocco Scalability

  • We need some metrics that give some insight into how things are scaling as the load starts to ramp. We should also discuss morgamic's idea for throttling based on update channel, or any other throttling mechanism we want to try and implement.
  • Throttling bug is

Quick Review of other Feature and Bug List and Priorities

[ | Current Buglist ]