3 ms·

Lower memory usage (I think).

• zanny 13y ago
  You know, because the reason there are threads in the first place is that a single running process can share its global variables and heap space. When Chrome runs in multiple processes, it has to duplicate its global (mostly static) variable space each time. Albeit, that is certainly peanuts next to the v8 interpreters heap, the web page itself, loaded images, etc, but there is a reason few programs do the multi-process thing. Chrome doesn't really get a speedup from it, it gets a stability bump. If one tab crashes in Chrome a tab goes, if a tab in firefox goes it drops the whole browser process. As a development design pattern, if you are concerned with stability, you fork your threads into their own processes and prepare for them to go down in flames.