canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
Electrolysis/Multiple content processes: Difference between revisions
Jump to navigation
Jump to search
Electrolysis/Multiple content processes (view source)
Revision as of 17:51, 2 February 2017
, 2 February 2017→M1[Nightly]: enable 2 content processes on nightly (target: Firefox 52, tracking: M1)
No edit summary |
|||
| Line 8: | Line 8: | ||
== Roadmap == | == Roadmap == | ||
=== M1[Nightly]: enable 2 content processes on nightly (target: Firefox | === M1[Nightly]: enable 2 content processes on nightly (target: Firefox 53, tracking: [https://bugzilla.mozilla.org/buglist.cgi?list_id=13206336&status_whiteboard_type=allwordssubstr&status_whiteboard=%5Be10s-multi%3AM1%5D&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED '''M1''']) === | ||
Apart a few corner cases 2 content processes are fairly stable for everyday usage. Our hope is that by enabling 2 content processes on nightly despite a few known issues that will be time consuming to fix (session storage / shared workers) we will get better bug reports early. | Apart a few corner cases 2 content processes are fairly stable for everyday usage. Our hope is that by enabling 2 content processes on nightly despite a few known issues that will be time consuming to fix (session storage / shared workers) we will get better bug reports early. | ||
* Ignore memory footprint. | * Ignore memory footprint. | ||
* Fix crash report in background tabs {{bug|1241459}} | * Fix crash report in background tabs {{bug|1241459}} | ||
* Known issues that will block riding the train but will not block enabling 2 content processes on nightly: | * '''Known issues that will block riding the train but will not block enabling 2 content processes on nightly:''' | ||
** Service/Shared workers should run in their own process: {{bug|1231208}} | ** Service/Shared workers should run in their own process: {{bug|1231208}} | ||
** Session storage is not designed for multiple content processes, next generation DOM storage will fix this problem: {{bug|1286798}} | ** Session storage is not designed for multiple content processes, next generation DOM storage will fix this problem: {{bug|1286798}} | ||