18
edits
Platform/Games/StatusUpdate: Difference between revisions
→Addressing 32-Bit Out of Memory Issues (OOMs)
| 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== | ||