1294023 - Audit and document the ramifications for opting in to content process isolation

Status: RESOLVED FIXED

(Core :: DOM: Content Processes, defect)

Description

[Jukka Jylänki]

In bug 1277066, a new meta tag "<meta name=freshProcess>" is being added which allows site developers to opt in to content process isolation specifically for the page in question.

This will help 32-bit browsers from running into problems with address space fragmentation problems in asm.js/wasm applications. However, the feature does have some drawbacks, one such is that synchronous access to properties in "window.opener" object is not possible in a child window that opted in to process isolation. See also bug 1294017. Another drawback is that the feature is not available if the page is loaded inside an iframe - the page must be a top level window for it to work.

What other effects (requirements/restrictions) will <meta name=freshProcess> have that developers will need to know and take into account? Let's gather them here as those are discovered to help on the developer education front.

Comment 1

[Jukka Jylänki]

This was resolved by Florian in https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Large-Allocation.