JM Casey <crystallogic@...>
toggle quoted messageShow quoted text
Interesting. This is also what Firefox started doing beginning with version 57, I believe. But it’s possible that Chrome opens more processes.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Mike B.
Sent: October 12, 2018 7:30 PM
Subject: [jaws-users] Chrome, Explanation as to Why it has so Many Processes Running
This article might give some of you an idea what all goes on in the background when Chrome is running.
I found this blog post, and thought others on this list might be
interested in what it has to say about why so many google processes open
up when running the browser.
In short, it opens a new process for each plugin and/or script on a web
page, to keep them isolated from the basic browser, thereby keeping the
computer as secure as possible from malicious pages.
Chromium Blog: Multi-process Architecture s1600-r/logo_chromium
Chromium Blog News and developments from the open source browser project
Multi-process Architecture Thursday, September 11, 2008 Unlike most current web browsers, Google Chrome uses many operating system processes to keep web sites separate from each other and from the rest of your computer. In this blog post, I'll explain why using a multi-process architecture can be a big win for browsers on today's web. I'll also talk about which parts of the browser belong in each process and in which situations Google Chrome creates new processes.
For all of these reasons, Google Chrome's multi-process architecture can help it be more robust, responsive, and secure than single process browsers.
Posted by Charlie Reis