CrashKill/2009-10-12: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 19: Line 19:
** some un-reproducible bugs : {{Bug|519729}} - {{Bug|519344}}
** some un-reproducible bugs : {{Bug|519729}} - {{Bug|519344}}
* _PR_MD_SEND - {{bug|489533}} - Jonas/jimm. Potentially bad LSP issues. jimm will be looking at it this week.
* _PR_MD_SEND - {{bug|489533}} - Jonas/jimm. Potentially bad LSP issues. jimm will be looking at it this week.
* nsWindow::GetParentWindow(int) - there is one crash on 3.6b1pre for this, bug id is {{470487}}, should be {{506108}} (destroy widget vs. create widget).

Revision as of 21:58, 12 October 2009

Misc

  • (Dolske) Got confused about exactly how throttling works, so looked into it...
    1. For release builds, we currently throttle at 15% on the server, and 10% on Windows clients. The client is unthrottled on OS X / Linux.
    2. For nightly and beta builds, the throttling is disabled on both the client and server.
    3. The client throttling actually just sets the default value of the "Submit Report" checkbox, for the very first time a user sees the crash reporter. The user can check (or uncheck) the checkbox, and we save that as the default for the next time they crash.
    4. Reports that were throttled by the server will be processed if explicitly requested by the client (eg, by clicking an about:crashes link). This is probably a small number in practice.
    5. So, ignoring user changes, that would imply the actual number of release-build crashes seen by users is ~150x the number reported by Socorro for Windows, and ~15x for OS X.

Breakpad & Socorro

Bugs

  • Tomcat
  • _PR_MD_SEND - bug 489533 - Jonas/jimm. Potentially bad LSP issues. jimm will be looking at it this week.
  • nsWindow::GetParentWindow(int) - there is one crash on 3.6b1pre for this, bug id is Template:470487, should be Template:506108 (destroy widget vs. create widget).