Chrome-process architecture, open a browser how many processes?
First, before 2007, the browser is a single process, instability, not smooth, unsafe
Second, the early multi-process browser (primary process, the rendering process, plug-in process)
1, isolated from each other prior to the process, so when a page or plug-in crashes, affecting only the current page process or plug-in process, and will not affect other browsers and page
2, the additional benefit of multi-process architecture is possible use security sandbox
3, JavaScript is also running in the rendering process, so even if JavaScript blocking the rendering process, affecting only the current render the page, the browser and does not affect other pages
Third, the current multi-process browser
Architecture are: the main process, GPU processes, network processes, the rendering process, plug-in process
The main process responsible for interface display, user interaction, child process management, while providing storage and other functions;
GPU process using the original intention was to achieve 3D CSS effects, but then the page, Chrome UI interface are selected using the GPU rendering;
rendering process core mission is to convert HTML, CSS and JavaScript for web users can interact, rendering processes are run in sandbox mode, by default, Chrome will create a rendering process for each Tab label;
network processes responsible for the page network resource loading;
plug-in process is responsible for running plug-ins
Usually we encounter a single page stuck cause the browser to crash because for homologous pages, share a rendering process, so when the collapse of a single page, it will lead to a page on the same site to crash.