multi-process browser architecture
The design in which a browser runs its tabs, extensions and networking in separate operating system processes instead of one big program.
In more detail
Splitting the browser into processes means one crashing tab cannot take the others down, and a compromised page is kept away from your files and other sites. A central browser process coordinates the address bar, storage and navigation. Renderer processes draw pages, and the processes talk to each other over IPC channels.
Related terms
- browser process — The main browser process that owns the address bar, tabs, disk storage and network access, and coordinates all the other processes.
- renderer process — The sandboxed process that turns one tab's HTML, CSS and JavaScript into pixels and runs the page's scripts.
- IPC channel — A message pipe that lets two separate processes, such as a browser's renderer and its browser process, send each other data.
- sandbox — A locked-down environment in which a program runs with very few permissions, so that damage from a bug or attack stays contained.
- process — A program that is currently running, with its own memory and a numeric identifier.
Taught in
- How Browsers Work: Navigation, DNS, TCP, TLS And Request Timing — Frontend Architecture & Web Platform
- Critical Rendering Path: Preload, Prefetch And Scripts — Frontend Architecture & Web Platform