4 ms·
Can someone explain the difference between the process / thread architecture of chrome and firefox desktop apps and the implications of this difference? On MacO
by Myrmornis 9y ago
Can someone explain the difference between the process / thread architecture of chrome and firefox desktop apps and the implications of this difference? On MacOS Chrome appears as many processes named Chrome helper or something, whereas Firefox appears as a single process with many threads. Given that the two are trying to solve the same problem and are so superficially similar, is the difference in architecture surprising?
- nnethercote 9y agoFirefox now uses multiple processes too. By default Firefox is limited to one UI process and four web content processes. Chrome will use roughly one content process per tab (though that's an oversimplification). Firefox's choice to use fewer web content processes result in less memory usage, but if a content process crashes you'll have to reload 1/4 of your tabs. Both browsers use threads extensively within each process as well.