18
edits
Platform/Games/StatusUpdate: Difference between revisions
→Migration to 64-Bit Browsers
| (One intermediate revision by the same user not shown) | |||
| Line 27: | Line 27: | ||
A consistent pain point for web developers using compiled code bases and asm.js is hitting out of memory conditions on 32-Bit browsers. To address this 32-Bit OOM challenge, we have proposed a new Large-Allocation header [https://gist.github.com/mystor/5739e222e398efc6c29108be55eb6fe3]. This header tells the browser to make a best-effort attempt to load the document in an unfragmented content process, which should greatly decrease the OOM failure rate for top-level browsing contexts. We aim to ensure that if the conditions for a cross-process navigation are met, web apps are able to reliably allocate a gigabyte of contiguous address space. | A consistent pain point for web developers using compiled code bases and asm.js is hitting out of memory conditions on 32-Bit browsers. To address this 32-Bit OOM challenge, we have proposed a new Large-Allocation header [https://gist.github.com/mystor/5739e222e398efc6c29108be55eb6fe3]. This header tells the browser to make a best-effort attempt to load the document in an unfragmented content process, which should greatly decrease the OOM failure rate for top-level browsing contexts. We aim to ensure that if the conditions for a cross-process navigation are met, web apps are able to reliably allocate a gigabyte of contiguous address space. | ||
'''Ship Status:''' | '''Ship Status:''' Firefox intends to ship the Large-Allocation header solution in Firefox 53 in April 2017. | ||
==Migration to 64-Bit Browsers== | ==Migration to 64-Bit Browsers== | ||
| Line 40: | Line 40: | ||
As nearly three-quarters of Firefox users are running 32-bit Firefox on 64-bit Windows, there is a huge opportunity to improve the ability of those users to run large web apps by accelerating the shift to 64-bit. | As nearly three-quarters of Firefox users are running 32-bit Firefox on 64-bit Windows, there is a huge opportunity to improve the ability of those users to run large web apps by accelerating the shift to 64-bit. | ||
'''Ship Status:''' Per our plan of record[https://wiki.mozilla.org/Firefox/Win64#Plan], we are targeting | '''Ship Status:''' Per our plan of record[https://wiki.mozilla.org/Firefox/Win64#Plan], we are targeting August 2017 (Firefox 55) to change the Firefox installer to default to 64-bit for new installs or reinstalls for eligible users. Upgrading existing 32-bit browser users on 64-bit OSes to a 64-bit browser is not part of this roll-out phase. Our current thinking is to upgrade 32-bit users in October 2017 (Firefox 56). | ||
==Standardizing and Shipping SharedArrayBuffer== | ==Standardizing and Shipping SharedArrayBuffer== | ||