3 ms·
Process-per-site isolation doesn't necessarily have to use (much) more memory. If you pre-initialize the renderer and JavaScript engine and then fork that pre-
by lxgr 2y ago
Process-per-site isolation doesn't necessarily have to use (much) more memory.
If you pre-initialize the renderer and JavaScript engine and then fork that pre-warmed instance for each site, every page of memory not written to remains shared in physical memory.
Properly accounting for that in task managers is hard, though; on many OSes, Chrome's memory usage looks much scarier than it is in reality.
- astrange 2y agoYou can't fork a GUI process on Apple OSes, most of the system can't handle it. It'd also weaken any security protection based on randomness (eg ASLR slide, pointer encryption keys).
- lxgr 2y agoHuh, TIL Chrome on macOS might actually not be using the “zygote process” paradigm! https://source.chromium.org/chromium/chromium/src/+/main:content/public/common/zygote/features.gni https://source.chromium.org/chromium/chromium/src/+/main:con...
- bdd8f1df777b 2y agoNot possible on Windows, where most Chrome users are on.