Firefox Core Engineering/Crash machinery roadmap

From New wiki
Jump to navigation Jump to search
The Firefox Core Engineering (FCE) team ran from March 2016 through January 2018. All work on that team has been dispersed to other teams.

This page should be considered legacy.

For more information on previously-FCE activities, go by individuals listed in Historical knowledge areas. (If you're in a pinch, ask ddurst.)

Crash machinery should be reliable, fast, and informative for both Mozilla and ultimately the user.

This effort began with Get More Data Faster, which is still in progress. The goal is to speed up crash telemetry receipt and provide a basis for near-realtime crash monitoring and trend analysis.

Major Milestones

The major milestones overall have been achieved:

  • introduce client-side stackwalking
  • create crash ping
  • land content crash ping
  • create PingSender
  • add support for CFI-based stackwalking

Minor Milestones

Along the way, a variety of related bugs have cropped up. They are this project's backlog and they are tracked here.

<bugzilla> { "blocks": "1416078", "resolution": "---", "include_fields": "id, product, summary, priority, status, whiteboard, keywords, assigned_to" } </bugzilla>

Future planning

  • https://bugzilla.mozilla.org/show_bug.cgi?id=1296274 (symbolicate on client, then signature on client, then show user the problems on (say) about:support ): Evalute symbolicating stack traces when doing client-side stack walking
  • replace BreakPad
  • rewrite minidump analyzer in Rust
  • rewrite CrashReporter in Rust
Retrieved from "https://mozilla.mediawiki.site/w/index.php?title=Firefox_Core_Engineering/Crash_machinery_roadmap&oldid=1188551"