Not what I meant. "The Mozilla platform will use separate processes to display the browser UI, web content, and plugins." [1] -- I don't like this idea myself a

Not what I meant. "The Mozilla platform will use separate processes to display the browser UI, web content, and plugins." [1] -- I don't like this idea myself as it creates odd inter-process communication. Each tab thread will need to contact the UI, web content, and plugin thread. To me, it makes more sense to have each tab be its own process. Threads don't provide a real advantage here. The executable is loaded once as the OS is smart enough to share the binary, common libraries are loaded once (using mmap), both processes and threads need their own stacks. However, by splitting loads as they have, if any of those 3 main processes fail, everything dies. 1.) https://wiki.mozilla.org/Content_Processes https://wiki.mozilla.org/Content_Processes