MDN’s new design is in Beta! A sneak peek:

Multiprocessos do Firefox

Esta tradução está incompleta. Por favor, ajude a traduzir este artigo do Inglês.

Nas versões atuais do Firefox para PC, todo o navegador funciona um único processo do sistema operativo. 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").

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.

Normal web pages are unaffected by multiprocess Firefox. People working on Firefox itself and Firefox add-on developers will be affected if their code relies on being able to access web content directly.

Instead of accessing content directly, chrome JavaScript will have to use the message manager to access content. To help ease the transition we've implemented Cross Process Object Wrappers and some compatibility shims for add-on developers. If you are an add-on developer wondering whether you are affected, see the guide to working with multiprocess Firefox.

Multiprocess Firefox is currently enabled by default in Developer Edition builds.

Resumo técnico
A very high-level view of how multiprocess Firefox is implemented.
Guia de compatibilidade do conteúdo da Web
Guidelines and details on potential Web site compatibility issues that may arise due to the transition. Tip: there aren't very many!
A reference for the jargon used in multiprocess Firefox.
Gestor de mensagem
Complete guide to the objects used to communicate between chrome and content.
Extras baseados em SDK
How to migrate add-ons developed using the Add-on SDK.
Quais os URIs que carregam e onde
A quick guide to which URIs - chrome:, about:, file:, resource: - are loaded into which process.
Why we are implementing multiprocess Firefox: performance, security, and stability.
Guia de migração de extra
If you are an add-on developer, find out if you are affected and how to update your code.
Cross Process Object Wrappers
Cross Process Object Wrappers are a migration aid, giving chrome code synchronous access to content.
Processos do conteúdo de depuração
How to debug code running in the content process, including frame and process scripts.
Seleção de separador nos multiprocessos do Firefox
How switching tabs works in multiprocess Firefox.

Limitações dos scripts do chrome
Practices that will no longer work in chrome code, and how to fix them.
Limitações dos scripts de frame
Practices that will not work inside frame scripts, and what to do instead.


Find out more about the project, get involved, or ask us your questions.

Etiquetas do documento e contribuidores

 Contribuidores para esta página: mansil, Sheppy
 Última atualização por: mansil,