Firefox/Win64

From MozillaWiki
< Firefox(Redirected from Firefox/win64)
Jump to: navigation, search

Objective

Make 64-bit Firefox the default version for new and existing eligible users to reduce our OOM crash rate, increase performance, and improve security (ASLR).

Users are eligible for a 64-bit default if they are running 64-bit Windows 7+ and have at least 2 GB RAM. For users with less than 4 GB of physical memory, there is a trade-off between the larger virtual address space and the overhead of 64-bit code. 2 GB RAM is Microsoft's minimum memory requirement for Windows 7 and 10.

Schedule

  • 2014 Q3
    • [DONE] August 8 - Chrome's 64-bit announcements: Mac and Windows
  • 2015 Q2
  • 2015 Q4
  • 2016 Q3
    • [DONE] July 20 - Announced NPAPI to be removed in Firefox 52: Reducing Adobe Flash Usage in Firefox
    • [DONE] August 29 - Web team will start redesigning download page redesign for 64-bit
    • [DONE] September 23 - Web team will start A/B test of new download page
  • 2016 Q4
    • [DONE] October 7 - Web team will complete A/B test of new download page
    • [DONE] October - Drop support for non-Flash NPAPI plugins in Nightly 52 (bug 1269807)
    • [DONE] October - Create dashboards for 64-bit rollout criteria
    • [DONE] November 24 - Make 64-bit the stub installer's default in Nightly 53 (bug 797208). The 64-bit default did not ride the trains with 53. The 64-bit installer option shipped in 54.
  • 2017 Q1
  • 2017 Q2
    • [DONE] April 12 - Enabled Flash async drawing in Aurora 54 (bug 1340934)
    • [DONE] April 18 - Firefox 53 release (with 64-bit installer option)
    • [DONE] May 2 - Google began migrating 32-bit Chrome users (with more than 4GB RAM) to 64-bit Chrome 58.
    • [DONE] May 8 - Flash release with fix for acceleration regression bug 1359886.
    • [DONE] June 13 - Firefox 54 release
    • [DONE] June 13 - Flash 26 (York) release should fix zero-sized Flash bug 1348629.
    • [DONE] June 22 - Started Funnelcake experiment to compare 32-bit vs 64-bit for eligible Release 54 users: 120K users in de, es-ES, fr, pt-BR, and ru. (bug 1309844 and bug 1309847)
    • [DONE] June - Write technical blog post about 64-bit installer default in 55.
  • 2017 H2
    • [DONE] August 8 - Firefox 55 release (with 64-bit installer default)
    • [DONE] August 14 - Publish technical blog post after 54 Funnelcake experiment: 64-bit Firefox is the new default on 64-bit Windows
    • [PROPOSED] July - Add section about 64-bit migration to Ryan's 56 release announcement.
    • [ON TRACK] October 3 - Firefox 56 release
    • [PROPOSED] October - Migrate eligible 32-bit Firefox users to 64-bit (bug 1274659) with a 56.0.1 dot release (so we can throttle migration).

Release Criteria

Migration Opt-Out

Users running 32-bit Firefox on Win64 OS with at least 2 GB RAM will be automatically upgraded/migrated to 64-bit Firefox 56.0.1. 32-bit Firefox users that do not wish to be migrated to 64-bit Firefox can opt-out of the migration setting a Windows registry key (added in bug 1386176) as described below.

If you have already been migrated to 64-bit Firefox 56.0.1 but prefer to run 32-bit Firefox, you can download 32-bit Windows Firefox 56.0.1 and re-install. Firefox will not attempt to migrate 32-bit users running version 56.0.1 or later!

Instructions for creating the migration opt-out registry key:

  • To disable migration for all Firefox installations on a client system for all users, create the following registry entry:
    • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Firefox\32to64DidMigrate
    • Value Type: DWORD (32 bit) Value
    • Value Name: Never
    • Value: 1
  • To disable migration for all Firefox installations on a client system only for the current user, create the following registry entry:
    • Path: HKEY_CURRENT_USER\SOFTWARE\Mozilla\Firefox\32to64DidMigrate
    • Value Type: DWORD (32 bit) Value
    • Value Name: Never
    • Value: 1
  • To disable migration for a single Firefox installation on a client system for all users, create the following registry entry:
    • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Firefox\32to64DidMigrate
    • Value Type: DWORD (32 bit) Value
    • Value Name: <Windows path to the installation directory without a trailing backslash> (Important: do NOT include a trailing backslash!)
      • example: C:\Program Files (x86)\Mozilla Firefox
    • Value: 1
  • To disable migration for a single Firefox installation on a client system only for the current user, create the following registry entry:
    • Path: HKEY_CURRENT_USER\SOFTWARE\Mozilla\Firefox\32to64DidMigrate
    • Value Type: DWORD (32 bit) Value
    • Value Name: <Windows path to the installation directory without a trailing backslash> (Important: do NOT include a trailing backslash!)
      • example: C:\Program Files (x86)\Mozilla Firefox
    • Value: 1

Links

Bugs

ID Priority Summary Whiteboard Keywords Assigned to

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


ID Priority Summary Whiteboard Keywords Assigned to
1360666 -- BigBlueButton Flash does not receive click events after switching tabs when 32-bit async drawing is enabled flashplayer, regression Jim Mathies [:jimm]
1394105 -- Firefox 55 - performance of Shockwave Flash content has dropped significantly, with web based flash running very slowly, disabling async drawing solves the issue dev-doc-complete, flashplayer, perf, regression, site-compat, user-doc-needed
1311975 P2 Cannot interact with Flash Video Controls on certain site gfx, STR in comment #0 (32bit only) regression
1306698 P3 When resize content/window, image under the flash plug-in is briefly display layout, STR in comment #0 regression
1347925 P3 wmode direct flash reverts to windowed mode if browser hardware acceleration is disabled
1347575 P4 Disabling acceleration in flash breaks flash settings dialog on live.nicovideo.jp jp-critical, regression

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


Team

Role Contact
Product Management Romain Testard
Engineering David Parks (Flash sandbox), Matt Howell and Robert Strong (installer), Stéphanie Ouillon (Flash sandbox review)
QA Ryan VanderMeulen
UX Michael Verdi (Firefox), Jon Petto (Mozilla.org)
Release Management Sylvestre Ledru
Release Engineering Chris AtLee
Firefox Program Management Chris Peterson
Mozilla.org Program Management Jennifer Bersch
Add-ons Jorge Villalobos