75
edits
Changes
Updating M1 to reflect our current status
== Roadmap ==
=== M1: general correctness enable 2 content processes on nightly (1target: Firefox 52, tracking: [https://bugzilla.mozilla.org/buglist.cgi?list_id=13206336&status_whiteboard_type=allwordssubstr&status_whiteboard=%5Be10s-multi%3AM1%5D&resolution=---2 months&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''']) ===* Fix correctness bugs (making Apart a few corner cases 2 content processes are fairly stable for everyday usage. Our hope is that by enabling 2 content processes correcton 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.
* Create framework for tab<->process selection code.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:** 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}}** Some test will need some refactoring: {{bug|1301015}} but for now we will force them to use single content process: {{bug|1301340}}
=== M2: preparation for scaling (3 months) ===
