How Web Browsers use Processes and Threads

Process And Threads

Process means any program is in execution. Process control block controls the operation of any process. Process control block contains the information about processes for example: Process priority, process id, process state, CPU, register etc. A process can creates other processes which are known as Child Processes. Process takes more time to terminate and it is isolated means it does not share memory with any other process.

Process and Threads in Chrome

By default, Chrome creates a process for each tab of a web site the user visits and plugins extensions it uses. This ensures that pages from different sites are rendered independently, and that separate visits to the same site are also isolated from each other. Thus, failures (e.g., site crashes) or heavy resource usage in one instance of a site will not affect the rest of the browser. There is also processes for main browser and GPU functionality.

Process and Threads Firefox

Historically, Firefox has been a single-process browser. As it turned out, running the browser UI plus the HTML rendering and JavaScript for all tabs in a single process is a bad idea. It easily freezes the UI, and it might not be optimal from a security point of view, either.

Chrome vs Firefox

While both Firefox and Chrome now run using multiple processes, Firefox does some things differently to avoid using up user computer’s limited memory.