Hi,

First it is important to understand that the total memory consumption is NOT the sum of all child processes. See here for more details:

https://www.essentialobjects.com/forum/postst8270p2_RunDLL32-and-Memory-Footprint-of-EOWebBrowser.aspx#43275

As to number of child process and exact memory consumption of each process, this completely depends on the Chromium browser engine. Chromium browser engine has a rather complex multi-process architecture and they adjust it from time to time. As the main purpose of using child process is to isolate different modules/site into different processes for security reasons, the general trend is as Chromium team fine tune security policies, more and more modules are being isolated into their own process.

As to exact memory consumption of each process we can not say for sure since Chromium project is extremely large (over 35 million lines of code) and it is constantly evolving. It would not be surprising that each version would increase a bit since the code base keeps growing. So it would cost more memory to just load the code into memory.

Hope this makes sense to you. Please feel free to let us know if you still have any more questions.

Thanks!