Google Chrome的许多过程(32位) [英] Many process of Google Chrome (32 bit)

问题描述

在Chrome中运行2个测试时，我发现任务管理器中运行的Google Chrome(32位)进程过多，这是Chome驱动程序的正确行为吗?

When 2 tests are running in Chrome, i have observed that too many Google Chrome(32 Bit) processes are running in Task manager, Is this a correct behavior of Chome Driver

推荐答案

通过 Google Chrome浏览器执行多个自动测试时，您必须观察到可能有数十个通过Windows任务管理器的Processes标签可以观察到的 Google Chrome 进程的运行情况.

When multiple automated tests are getting executed through Google Chrome you must have observed that there are potentially dozens of Google Chrome processes running which can be observed through Windows Task Manager's Processes tab.

快照:

根据文章解决:为什么Google Chrome浏览器具有如此多的处理程序以获得更好的用户体验 Google Chrome浏览器会引发很多自动测试打开的每个选项卡中标记为'windows'" rel ="tag"> windows 的后台进程的问题. Google尝试通过将每个网页分成它认为合适的多个进程来保持浏览器的稳定，以确保如果某个进程在页面上失败，则可以终止或刷新该特定进程而无需终止或刷新整个进程页面.

As per the article SOLVED: Why Google Chrome Has So Many Processes for a better user experience Google Chrome initiates a lot of windows background processes for each tab that have been opened by your Automated Tests. Google tries to keep the browser stable by separating each web page into as many processes as it deems fit to ensure that if one process fails on a page, that particular process(es) can be terminated or refreshed without needing to kill or refresh the entire page.

但是，从2018年开始， Google Chrome 实际上经过了重新设计，以为以下每个实体创建新流程:

However, from 2018 onwards Google Chrome was actually redesigned to create a new process for each of the following entities:

• Tab
• 页面上的HTML/ASP文本
• 将这些插件插入
• 已加载的应用
• 页面内的框架

在铬博客中多-流程架构:

Google Chrome浏览器利用这些属性，将Web应用程序和插件与浏览器本身置于不同的进程中.这意味着一个Web应用程序中的渲染引擎崩溃不会影响浏览器或其他Web应用程序.这意味着操作系统可以并行运行Web应用程序以提高其响应速度，并且这意味着如果特定的Web应用程序或插件停止响应，浏览器本身将不会锁定.这也意味着我们可以在限制性沙箱中运行渲染引擎进程，以帮助限制发生漏洞利用时的损害.

Google Chrome takes advantage of these properties and puts web apps and plug-ins in separate processes from the browser itself. This means that a rendering engine crash in one web app won't affect the browser or other web apps. It means the OS can run web apps in parallel to increase their responsiveness, and it means the browser itself won't lock up if a particular web app or plug-in stops responding. It also means we can run the rendering engine processes in a restrictive sandbox that helps limit the damage if an exploit does occur.

结论是，您看到的许多过程与

As a conclusion, the many processes you are seeing is pretty much in line with the current implementation of

您可以在 查看全文