3 ms·
I thought the plan was for Firefox to use the same process-per-tab model as Chrome, but this post does seem to imply that it's just 2 - "we’re using project Ele
by wjoe 10y ago
I thought the plan was for Firefox to use the same process-per-tab model as Chrome, but this post does seem to imply that it's just 2 - "we’re using project Electrolysis to split Firefox into a UI process and a content process."
They also go on to say that "After that, we’ll be working on support for multiple content processes.", so I assume the plan is to have one perocess-per-tab eventually. I'm surprised they aren't there already though, considering this has been in the works for a few years now.
- keeperofdakeys 10y agoThere was a period where electrolysis didn't receive much work, and then there was a second push to get it working. That's why it seems to be taking so long. As for process-per-tab, I can't find anything official about it on the bug tracker. The problem with that option is it leads to quite high memory usage, and hides the existence of memory leaks (chrome really likes to eat my ram). We'll have to see how memory usage goes as they experiment with multiple content processes.
- c0nducktr 10y agoIt is starting with just two for now, but will be increased after more optimization. There's a setting you can modify in about:config that will allow you to manually set the number of processes if you want to experiment with it. source: https://www.reddit.com/r/firefox/comments/4hmii4/firefoxs_appeal_has_been_plummeting_according_to/d2r0sad https://www.reddit.com/r/firefox/comments/4hmii4/firefoxs_ap...