{"json_modified": "2015-05-21T10:15:43.198748", "slug": "Mozilla/Firefox/Multiprocessus_Firefox", "tags": [], "locale": "fr", "title": "Firefox multi-processus", "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 to have more than one content process. The project that's delivering multiprocess Firefox is called Electrolysis, sometimes abbreviated to e10s.", "localization_tags": [], "locale": "en-US", "last_edit": "2015-05-20T21:45:52", "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": "2015-05-17T01:54:59", "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": []}, {"title": "Multiprocess Firefox", "url": "/pt-BR/Firefox/Multiprocess_Firefox", "tags": ["Portugu\u00eas (do Brasil) 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": ["inprogress"], "locale": "pt-BR", "last_edit": "2015-04-26T16:08:54", "review_tags": ["editorial"]}, {"title": "Multiprocess Firefox", "url": "/it/Firefox/Multiprocess_Firefox", "tags": [], "summary": "Nelle attuali versioni di Firefox Desktop, l'intero browser gira in un singolo processo del sistema operativo. In particolare, JavaScript che avvia la UI del browser (conosciuta anche come \"codice chrome\") gira nello stesso processo cos\u00ec come nelle pagine web (meglio conosciute come \"contenuto\" o \"contenuto web\").<br/><br/>\n Le future versioni di Firefox avvieranno la UI del browser in un processo separato dal contenuto web. Nella iniziale iterazione di questa architettura tutte le schede del browser funzioneranno nello stesso processo, e la UI del browser girer\u00e0 in un processo differente. Nelle prossime iterazioni, ci aspettiamo di avere pi\u00f9 di un unico processo di contenuti. Il progetto di Firefox multiprocesso che stiamo consegnando \u00e8 chiamato Electrolysis, a volte abbreviato in e10s.", "localization_tags": ["inprogress"], "locale": "it", "last_edit": "2015-05-19T05:44:28", "review_tags": ["editorial"]}], "modified": "2015-05-21T10:15:42", "label": "Firefox multi-processus", "localization_tags": ["inprogress"], "url": "/fr/Firefox/Multiprocessus_Firefox", "last_edit": "2015-05-21T10:15:41", "summary": "Dans les versions actuelles de Firefox pour bureau, le navigateur ne s'ex\u00e9cute que dans un seul processus du syst\u00e8me d'exploitation. En particulier, le JavaScript ex\u00e9cutant le navigateur UI (\u00e9galement connu sous le nom \"code chrome\") s'ex\u00e9cute dans le m\u00eame processus que celui pr\u00e9sent dans les pages Web (<span class=\"spellmodupdated\" title=\"\">appel\u00e9</span> aussi \"contenu\" ou \"contenu Web\").", "sections": [{"id": "Contactez-nous", "title": "Contactez-nous"}], "id": 151241, "review_tags": ["technical", "editorial"]}