There used to be a setting to tweak Chrome's process behavior. I believe the default behavior is "Coalesce tabs into the same content process if they're from t

There used to be a setting to tweak Chrome's process behavior. I believe the default behavior is "Coalesce tabs into the same content process if they're from the same trust domain". Then you can make it more aggressive like "Don't coalesce tabs ever" or less aggressive like "Just have one content process". I think. I'm not sure how Firefox decides when to spawn new processes. I know they have one GPU process and then multiple untrusted "content processes" that can touch untrusted data but can't touch the GPU. I don't mind it. It's a trade-off between security and overhead. The IPC is pretty efficient and the page cache in both Windows and Linux _should_ mean that all the code pages are shared between all content processes. Static pages actually feel light to me. I think crappy webapps make the web slow, not browser security. (inb4 I'm replying to someone who works on the Firefox IPC team or something lol)