![]() ![]() At worst, you could lose hours of work on a project. If everything is running inside of a single process, a crash on one page will result in your entire browser crashing. If something does go wrong, it often results in a crash. Websites are complicated, and the more complex a website is, the more ways things can go wrong. It turns out that separating them confers a lot of advantages that can broadly be broken into three categories. Plugins, like Java, add additional functionality to the browser. The rendering engine - formally named Blink - interprets the code running on the website and displays the human-friendly version. The browser portion of Chrome is the part that actually handles the traffic going to and from the website. This occurs because Google Chrome deliberately separates the browser, the rendering engine, and the plugins from each other by running them in separate processes. You may have noticed that Google Chrome will often have more than one process open, even if you only have one tab open. Increased complexity means that the demand placed on your computer has increased too. Modern websites a quite complex - they have tons of “moving parts” that interact with each other, and with the user. What’s the deal with all those processes? Why Multiple Processes? If you’ve ever taken a peek in Task Manager while running Google Chrome, you may have been surprised to see that the number of chrome.exe entries radically exceeded the number of actual Chrome windows you had open.
0 Comments
Leave a Reply. |