{"json_modified": "2015-04-26T16:08:57.219045", "slug": "Mozilla/Firefox/Multiprocess_Firefox", "tags": ["Portugu\u00eas (do Brasil) tags"], "locale": "pt-BR", "title": "Multiprocess Firefox", "translations": [{"title": "Multiprocess Firefox", "url": "/en-US/Firefox/Multiprocess_Firefox", "tags": [], "summary": "In current versions of desktop Firefox, the entire browser runs in a single operating system process. In particular, the JavaScript that runs the browser UI (also known as \"chrome code\") runs in the same process as the code in web pages (also known as \"content\" or \"web content\").<br/><br/>\n Future versions of Firefox will run the browser UI in a separate process from web content. In the first iteration of this architecture all browser tabs will run in the same process, and the browser UI will run in a different process. In future iterations, we expect every browser tab to run in its own process. The project that's delivering multiprocess Firefox is called Electrolysis, sometimes abbreviated to e10s.", "localization_tags": [], "locale": "en-US", "last_edit": "2015-03-05T14:57:48", "review_tags": []}, {"title": "Multiprocess Firefox", "url": "/ru/docs/User:wbamberg/Multiprocess_Firefox", "tags": [], "summary": "In current and previous versions of desktop Firefox, the entire browser runs in a single operating system process. In particular, the code that runs the browser UI (also known as chrome code) runs in the same process as the code in web pages (also known as \"content\" or \"web content\").<br/><br/>\n Future versions of Firefox will run the browser UI in a separate process from web content. In the first iteration of this architecture all browser tabs will run in the same process, and the browser UI will run in another process. In future iterations, we expect every browser tab to run in its own process. The project that's delivering this change is called Electrolysis, sometimes abbreviated to e10s.<br/><br/>\n This change will make no difference to normal web pages, but it will have an effect on people working on Firefox itself and Firefox add-on developers, if their code relies on being able to access web content directly.", "localization_tags": ["inprogress"], "locale": "ru", "last_edit": "2014-09-19T20:18:49", "review_tags": []}, {"title": "Multiprocess Firefox", "url": "/de/Firefox/Multiprocess_Firefox", "tags": ["TopicStub", "NeedsTranslation"], "summary": "In current versions of desktop Firefox, the entire browser runs in a single operating system process. In particular, the JavaScript that runs the browser UI (also known as \"chrome code\") runs in the same process as the code in web pages (also known as \"content\" or \"web content\").<br/><br/>\n Future versions of Firefox will run the browser UI in a separate process from web content. In the first iteration of this architecture all browser tabs will run in the same process, and the browser UI will run in a different process. In future iterations, we expect every browser tab to run in its own process. The project that's delivering multiprocess Firefox is called Electrolysis, sometimes abbreviated to e10s.", "localization_tags": ["inprogress"], "locale": "de", "last_edit": "2014-12-15T16:38:56", "review_tags": []}, {"title": "Multiprocess Firefox", "url": "/zh-CN/Firefox/Multiprocess_Firefox", "tags": ["TopicStub", "NeedsTranslation"], "summary": "In current versions of desktop Firefox, the entire browser runs in a single operating system process. In particular, the JavaScript that runs the browser UI (also known as \"chrome code\") runs in the same process as the code in web pages (also known as \"content\" or \"web content\").<br/><br/>\n Future versions of Firefox will run the browser UI in a separate process from web content. In the first iteration of this architecture all browser tabs will run in the same process, and the browser UI will run in a different process. In future iterations, we expect every browser tab to run in its own process. The project that's delivering multiprocess Firefox is called Electrolysis, sometimes abbreviated to e10s.", "localization_tags": ["inprogress"], "locale": "zh-CN", "last_edit": "2015-01-06T13:29:11", "review_tags": []}], "modified": "2015-04-26T16:08:54", "label": "Multiprocess Firefox", "localization_tags": ["inprogress"], "url": "/pt-BR/Firefox/Multiprocess_Firefox", "last_edit": "2015-04-26T16:08:54", "summary": "In current versions of desktop Firefox, the entire browser runs in a single operating system process. In particular, the JavaScript that runs the browser UI (also known as \"chrome code\") runs in the same process as the code in web pages (also known as \"content\" or \"web content\").<br/><br/>\n Future versions of Firefox will run the browser UI in a separate process from web content. In the first iteration of this architecture all browser tabs will run in the same process, and the browser UI will run in a different process. In future iterations, we expect every browser tab to run in its own process. The project that's delivering multiprocess Firefox is called Electrolysis, sometimes abbreviated to e10s.", "sections": [{"id": "Contact_us", "title": "Contact us"}], "id": 148359, "review_tags": ["editorial"]}