Firefox Core Engineering: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(updated GMDF)
(Updated her name too)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{FirefoxCoreEngineering_banner}}
== Function ==
== Function ==
The purpose of this team is to address needs that fall between Toolkit and Platform, with an emphasis (currently) on improving stability, quality, and performance – supported by empirical data. As such, we overlap a bit with everyone from Gecko, Desktop, Data, and more.
The purpose of this team is to address needs that fall between Toolkit and Platform, with an emphasis (currently) on improving stability, quality, and performance – supported by empirical data. As such, we overlap a bit with everyone from Gecko, Desktop, Data, and more.
Line 8: Line 9:
* Adam Gashlin (:agashlin)
* Adam Gashlin (:agashlin)
* Felipe Gomes (:felipe)
* Felipe Gomes (:felipe)
* Matt Howell (:mhowell)
* Molly Howell (:mhowell)
* Chris HC (:chutten) -- honorary
* Chris HC (:chutten) -- honorary
* Kirk Steuber (:bytesized)
* Robin Steuber (:bytesized)
* Robert Strong (:rstrong)
* Robert Strong (:rstrong)
* Gabriele Svelto (:gsvelto)
* Gabriele Svelto (:gsvelto)
Line 41: Line 42:
There is currently no regimented process for regular triage of candidate work. Needs usually filter down through performance analysis and experimentation.
There is currently no regimented process for regular triage of candidate work. Needs usually filter down through performance analysis and experimentation.


[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=all_fce-active&sharer_id=500559 All actively tracked work is marked with the whiteboard "<nowiki>[fce-active]</nowiki>"] (for now). Or look at the [[#Active Bug List]] on this page.
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=all_fce-active&sharer_id=500559 All actively tracked work is marked with the whiteboard "<nowiki>[fce-active-legacy]</nowiki>"] (for now). Or look at the [[#Active Bug List]] on this page.


Major initiatives are listed on this page.
Major initiatives are listed on this page.
Line 60: Line 61:
* stack-walking, breakpad, and crash pings (gsvelto, ccorcoran)
* stack-walking, breakpad, and crash pings (gsvelto, ccorcoran)
* flash plugin-related (bytesized, felipe, dthayer)
* flash plugin-related (bytesized, felipe, dthayer)
* policy engine and MVP (felipe, bytesized)
* migration performance, BHR dashboard (dthayer)


== Pipeline ==
== Pipeline ==
=== Get More Data Faster ===
=== Get More Data Faster ===
We need to reduce known blind spots and barriers to getting data AND commit to non-ADI based metrics. For this, our goals are to:
We need to reduce known blind spots and barriers to getting data AND commit to non-ADI based metrics. For this, our goals are to:
* <strike>enable client-side stackwalking and send basic stack traces with crash pings (beginning in Nightly/Aurora, see {{Bugzilla|1280484}})</strike>
* <strike>enable content process crash reports ({{Bugzilla|1293656}})</strike>
* <strike>differentiate between process types in crash pings ({{Bugzilla|1310664}})</strike>
* process stack data in crash pings into a queryable result ({{Bugzilla|1310695}})
* process stack data in crash pings into a queryable result ({{Bugzilla|1310695}})
* <strike>create pingSender to handle crash pings instead of Gecko ({{Bugzilla|1310703}})</strike>
* <strike>enable client-side stackwalking and send basic stack traces with crash pings on all channels</strike>


See the [[Firefox_Core_Engineering/Get_More_Data_Faster|roadmap here]].
See the [[Firefox_Core_Engineering/Get_More_Data_Faster|legacy roadmap here]].


=== Set Flash to CTA by default ===
=== Set Flash to CTA by default ===
This includes:
This includes:
* prefer fallback content to Flash ({{Bugzilla|1277346}})
* prefer fallback content to Flash ({{Bugzilla|1277346}})
* <strike>establish allowedlists and deniedlists ({{Bugzilla|1307604}}, {{Bugzilla|1307605}})</strike>
* <strike>use heuristics to control when Flash is set to Click To Activate ({{Bugzilla|1307606}})</strike>
* <strike>geography-specific SHIELD study in FF53 release to understand user response and impact ({{Bugzilla|1335232}})</strike>


See the [https://docs.google.com/document/d/1sYp0DNioPA5iF3iw9LHGf1uN5B5AgdCu7jJxAh0MiqA/edit details here].
See the [https://docs.google.com/document/d/1sYp0DNioPA5iF3iw9LHGf1uN5B5AgdCu7jJxAh0MiqA/edit details here].


<!--
=== XBL/XUL replacement ===
==== XUL performance tests ====
TBD with and after Browser Architecture's recommendations.
XUL is supposed to go away, but it would seem that we don't know what the performance implications could/will be. This work builds on Neil Deakin's 2015 experiment to shed some light on where we need to focus our optimization/change efforts.
 
-->
=== Policy Engine ===
When implemented, this should provide an API for pre-defined policies to support enterprise management of Firefox deployments.
 
=== Migration performance optimization ===
With bug {{Bugzilla|1332225}}, investigate and optimize the migration process for new users.
 


=== App Updater and Installers ===
=== App Updater and Installers ===
Line 91: Line 92:
==== Update Orphan remediation ====  
==== Update Orphan remediation ====  
Remediation efforts have been tested for both system add-on capable and non (44.x and 43.0.1, respectively). Efforts are identified by ongoing analysis, including the [https://telemetry.mozilla.org/update-orphaning/ update orphaning dashboard]. This has yielded such things as:
Remediation efforts have been tested for both system add-on capable and non (44.x and 43.0.1, respectively). Efforts are identified by ongoing analysis, including the [https://telemetry.mozilla.org/update-orphaning/ update orphaning dashboard]. This has yielded such things as:
* continue the download instead of starting over after other networking errors occur ({{Bugzilla|1309124}})
* continue the download instead of starting over after other networking errors occur ({{Bugzilla|1309124}}, <strike>{{Bugzilla|1348087}}</strike>)
* create an Update Agent, responsible for running independently, daily, and downloading an update if found ({{Bugzilla|1343669}})
* create an Update Agent, responsible for running independently, daily, and downloading an update if found ({{Bugzilla|1343669}})
* <strike>continue the download instead of starting over after NS_ERROR_DOCUMENT_NOT_CACHED occurs ({{Bugzilla|1272585}})</strike> (FF49)
* create a dashboard for non-orphan telemetry analysis
* <strike>download the update MAR file unthrottled (already landed) ({{Bugzilla|1309125}}, {{Bugzilla|1309668}})</strike>
* <strike>serve a partial MAR file to Firefox 43.0.1 clients ({{Bugzilla|1309130}})</strike>
* <strike>push either a system or hotfix add-on that changed the download throttle preference to 0 for FF 50+</strike>
* <strike>run another method (non sysaddon, non SHIELD?, etc) to urge 43.0.1 users to upgrade</strike>
* <strike>Updater UI is outdated, too big, and needs to be updated ({{Bugzilla|893505}}) (FF55)</strike>
* <strike>change compression to LZMA for updates ({{Bugzilla|641212}}) (FF56)</strike>
* <strike>move to SHA-384 for MAR signing ({{Bugzilla|1324498}}) (FF56)</strike>
 
==== Installer UI ====
* <strike>Streamlined installer testing in QX onboarding funnelcake ({{Bugzilla|1328445}})</strike>


==== Windows 64 ====
==== Installer ====
We want to start moving users to 64-bit when appropriate:
* <strike>rename installed links to "Firefox" instead of "Mozilla Firefox" ({{Bugzilla|1413295}})</strike>
* <strike>stub installer should automatically select 32-bit or 64-bit ({{Bugzilla|797208}})</strike>
* stub installer metrics ({{Bugzilla|995794}})
* investigate MSI-based (read: non-NSIS) installer




== Current projects ==
== Current projects ==
=== 2017 Q4 goals ===
=== 2018 Q1 goals ===
* APP UPDATE (see [[Firefox_Core_Engineering/App_Updater_roadmap|roadmap]]):
* APP UPDATE (see [[Firefox_Core_Engineering/App_Updater_roadmap|legacy roadmap]]):
** Allow update download to continue in the background (beyond Firefox session)
** Allow update download to continue in the background (beyond Firefox session)
* INSTALLER (see [[Firefox_Core_Engineering/App_Installer_roadmap|roadmap]]):
* INSTALLER (see [[Firefox_Core_Engineering/App_Installer_roadmap|legacy roadmap]]):
** Outline plan for MSI-based installer
** Outline plan for MSI-based installer
** Support onboarding
** Support onboarding
* CRASH MACHINERY (see [[Firefox_Core_Engineering/Crash_machinery_roadmap|roadmap]]):
* CRASH MACHINERY (see [[Firefox_Core_Engineering/Crash_machinery_roadmap|legacy roadmap]]):
** Land support for CFI-based stackwalking
** (Implement crash ping signatures) -- relies on Data Pipeline
** (Implement crash ping signatures) -- relies on Data Pipeline
** (Start querying stacks received from crash pings for stability monitoring) -- relies on PI
** (Start querying stacks received from crash pings for stability monitoring) -- relies on PI
Line 125: Line 116:
** Assist with performance improvements for migration
** Assist with performance improvements for migration
* ENTERPRISE:
* ENTERPRISE:
** Prototype policy engine and policies MVP
** Prototype policy engine and policies MVP (for 59 beta tests, release in 60)
* XUL:
* XUL:
** Assist Browser Architecture team's flexbox recommendation effort
** Assist Browser Architecture team's flexbox recommendation effort
Line 133: Line 124:


* cmore is pitching that Firefox optimizes the user paths that support retention -- which could also include fixing paths where retention drops. This work probably involves a system add-on that initiates event-based recordation, as well as the analysis and remediation of the root cause (this is pending dcamp approval).
* cmore is pitching that Firefox optimizes the user paths that support retention -- which could also include fixing paths where retention drops. This work probably involves a system add-on that initiates event-based recordation, as well as the analysis and remediation of the root cause (this is pending dcamp approval).
* Firefox needs a "policy engine" (with API) to facilitate enterprise admins using Group Policies to ease deployment of Firefox in enterprise settings.
* Update (rstrong) needs help with https://bugzilla.mozilla.org/show_bug.cgi?id=1112937 -- ideally for FF58.
* DLL injection (see https://bugzilla.mozilla.org/show_bug.cgi?id=1306406) needs investigation/implementation of a dynamically updateable DLL blocklist (possibly using Kinto?).
* DLL injection (see https://bugzilla.mozilla.org/show_bug.cgi?id=1306406) needs investigation/implementation of a dynamically updateable DLL blocklist (possibly using Kinto?).
* On a personal note, if anyone experiences sluggishness in FF (on any channel) when you don’t restart it for a few days (maybe with several tabs open?), especially on Windows, please let me know ({{Bugzilla|1398652}}).
* Mossop (& browser arch) has begun the de-XBL. Overall browser architecture (& UI architecture) could be game in the near future.
* Mossop (& browser arch) has begun the de-XBL. Overall browser architecture (& UI architecture) could be game in the near future.


Line 143: Line 131:
<bugzilla>
<bugzilla>
{
{
"whiteboard": "[fce-active]",
"whiteboard": "[fce-active-legacy]",
"resolution": "---",
"resolution": "---",
"include_fields": "id, product, summary, priority, status, whiteboard, keywords, assigned_to"
"include_fields": "id, product, summary, priority, status, whiteboard, keywords, assigned_to"
}
}
</bugzilla>
</bugzilla>

Latest revision as of 17:21, 18 November 2025

Stop (medium size).png
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.)

Function

The purpose of this team is to address needs that fall between Toolkit and Platform, with an emphasis (currently) on improving stability, quality, and performance – supported by empirical data. As such, we overlap a bit with everyone from Gecko, Desktop, Data, and more.

This team grew out of, in part, the Performance Engineering team, and owns some of that team's infrastructure – some performance-related dashboards on telemetry.mozilla.org, crash analysis, hang visualization, etc. It also includes the installer & updater applications.

Personnel

  • Neil Deakin (:enn)
  • Adam Gashlin (:agashlin)
  • Felipe Gomes (:felipe)
  • Molly Howell (:mhowell)
  • Chris HC (:chutten) -- honorary
  • Robin Steuber (:bytesized)
  • Robert Strong (:rstrong)
  • Gabriele Svelto (:gsvelto)
  • Doug Thayer (:dthayer)
  • David Durst (:ddurst)

Goals

  1. Enabling stability
    In general, things we do should be tied to enabling stability – so, making it measurable and/or addressing issues.
  2. Supporting performance improvements
    Improving performance is certainly everyone's job—not just our team—but we hold the keys for some distinct historical pieces of the analysis that allow people to understand what needs to be improved. This is primarily, but not limited to, telemetry and data analysis.
  3. Improving the user/contributor experience
    This one is the weirdest: it covers things that we can do to further the web, and improve the experience for our users – both end users and code contributors (some examples: Flash blocking, XUL performance analysis). This category is the most open-ended for future expansion.

Communication

You can typically find us in:

IRC

  • #fce (primary)
  • #developers
  • #e10s
  • #fx-team
  • #perf
  • #releng
  • #telemetry
  • #uptime

Mailing lists

  • dev-platform
  • fhr-dev
  • firefox-dev

Process and Queuing

There is currently no regimented process for regular triage of candidate work. Needs usually filter down through performance analysis and experimentation.

All actively tracked work is marked with the whiteboard "[fce-active-legacy]" (for now). Or look at the #Active Bug List on this page.

Major initiatives are listed on this page.

Owned Infrastructure (needs updating per 1298080)

telemetry.mozilla.org Dashboards

  • Update Orphaning: functional

symbolapi.mozilla.org

This is the symbolication server (aka "Snappy Symbolication Server") used by platform developers and performance dashboards. It is not used for the analogous process on Socorro. This is currently slated to be replaced by the owner of symbols, peterbe. See Tecken.

Historical knowledge areas

  • back-end of the user interface/XUL, et al (enn)
  • e10s system add-ons & system add-ons for feature rollout (felipe)
  • e10s data analysis (chutten)
  • install and update (rstrong, mhowell)
  • telemetry, histograms, pings, and data reporting (chutten)
  • stack-walking, breakpad, and crash pings (gsvelto, ccorcoran)
  • flash plugin-related (bytesized, felipe, dthayer)
  • policy engine and MVP (felipe, bytesized)
  • migration performance, BHR dashboard (dthayer)


Pipeline

Get More Data Faster

We need to reduce known blind spots and barriers to getting data AND commit to non-ADI based metrics. For this, our goals are to:

  • process stack data in crash pings into a queryable result (1310695)

See the legacy roadmap here.

Set Flash to CTA by default

This includes:

  • prefer fallback content to Flash (1277346)

See the details here.

XBL/XUL replacement

TBD with and after Browser Architecture's recommendations.

Policy Engine

When implemented, this should provide an API for pre-defined policies to support enterprise management of Firefox deployments.

Migration performance optimization

With bug 1332225, investigate and optimize the migration process for new users.


App Updater and Installers

Update Orphan remediation

Remediation efforts have been tested for both system add-on capable and non (44.x and 43.0.1, respectively). Efforts are identified by ongoing analysis, including the update orphaning dashboard. This has yielded such things as:

  • continue the download instead of starting over after other networking errors occur (1309124, 1348087)
  • create an Update Agent, responsible for running independently, daily, and downloading an update if found (1343669)
  • create a dashboard for non-orphan telemetry analysis

Installer

  • rename installed links to "Firefox" instead of "Mozilla Firefox" (1413295)
  • stub installer metrics (995794)
  • investigate MSI-based (read: non-NSIS) installer


Current projects

2018 Q1 goals

  • APP UPDATE (see legacy roadmap):
    • Allow update download to continue in the background (beyond Firefox session)
  • INSTALLER (see legacy roadmap):
    • Outline plan for MSI-based installer
    • Support onboarding
  • CRASH MACHINERY (see legacy roadmap):
    • (Implement crash ping signatures) -- relies on Data Pipeline
    • (Start querying stacks received from crash pings for stability monitoring) -- relies on PI
  • PERFORMANCE:
    • Assist with measuring (and identifying) jank and hang via BHR
    • Assist with performance improvements for migration
  • ENTERPRISE:
    • Prototype policy engine and policies MVP (for 59 beta tests, release in 60)
  • XUL:
    • Assist Browser Architecture team's flexbox recommendation effort

Potential future projects

This list should be considered a work in progress. Decisions will be reflected for a particular quarter.

  • cmore is pitching that Firefox optimizes the user paths that support retention -- which could also include fixing paths where retention drops. This work probably involves a system add-on that initiates event-based recordation, as well as the analysis and remediation of the root cause (this is pending dcamp approval).
  • DLL injection (see https://bugzilla.mozilla.org/show_bug.cgi?id=1306406) needs investigation/implementation of a dynamically updateable DLL blocklist (possibly using Kinto?).
  • Mossop (& browser arch) has begun the de-XBL. Overall browser architecture (& UI architecture) could be game in the near future.


(partial) Active Bug List

Full Query
ID Product Summary Priority Status Whiteboard Keywords Assigned to
799861 Firefox Stub installer does not detect proxy (Win7) P3 NEW [stubv3-][fce-active-legacy]
1256952 Core [e10s] Caret breaks in contenteditable elements when I drag anything over them (without dropping) P2 REOPENED [fce-active-legacy]
1258895 Core Make test_bug426082.html and test_bug656379-1.html work with e10s P5 NEW btpp-active [fce-active-legacy]
1301572 Toolkit Stop update staging when there is a shutdown request P3 NEW [fce-active-legacy]
1310680 Mozilla Metrics Update all usage of datasets that rely on crash ping aggregation -- NEW [fce-active-legacy]
1316366 Toolkit include information from update-settings.ini in update ping? P3 NEW [fce-active-legacy]
1324801 Toolkit Telemetry should throttle pings to a sane limit per day P3 NEW [measurement:client][fce-active-legacy]
1416078 Firefox [meta] modernize crash handling and related areas P2 NEW [fce-active-legacy] meta

8 Total; 8 Open (100%); 0 Resolved (0%); 0 Verified (0%);

Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox_Core_Engineering&oldid=1255687"