Chrome process architecture

As you can see from the diagram , Abreast of the times Chrome The browser includes ：1 A browser （Browser） The main process 、1 individual GPU process 、1 A network （NetWork） process 、 Multiple rendering processes and multiple plug-in processes .

Let's analyze the functions of these processes one by one .

1. Browser process . Mainly responsible for interface display 、 User interaction 、 Subprocess Management , At the same time, it provides storage and other functions .
2. Rendering Progress . The core task is to HTML、CSS and JavaScript Turn it into a web page that users can interact with , Layout engine Blink and JavaScript engine V8 Are running in the process , By default ,Chrome For every one of them Tab Tag to create a rendering process . For safety reasons , The rendering process runs in sandbox mode .
3. GPU process . Actually ,Chrome At the beginning of the release, there was no GPU Process . and GPU The original intention of using is to realize 3D CSS The effect of , Just the following pages 、Chrome Of UI All interfaces are selected GPU To draw , This makes GPU Become a common requirement for browsers . Last ,Chrome In its multiprocess architecture, it also introduces GPU process .
4. Network process . Mainly responsible for loading web resources of the page , It used to run as a module in the browser process , Until recently, I was independent , Become a separate process .
5. Plug in process . Mainly responsible for the operation of plug-ins , Because plug-ins are easy to crash , So it needs to be isolated through the plug-in process , To ensure that the plug-in process crash will not affect the browser and page .