Firefox 66 released

Posted Mar 19, 2019 19:10 UTC (Tue) by mathstuf (subscriber, #69389)
Parent article: Firefox 66 released

> Improved performance and reduced crash rates by doubling web content loading processes from 4 to 8

Interesting to read that increasing the number of threads reduced crash rates :) .

Firefox 66 released

Posted Mar 19, 2019 20:47 UTC (Tue) by MatejLach (guest, #84942) [Link]

I'd imagine because less tabs rely on one process, so when there's more processes, there's less tabs per one that could crash.

Firefox 66 released

Posted Mar 19, 2019 22:07 UTC (Tue) by atai (subscriber, #10977) [Link] (2 responses)

4 to 8: that can increase memory use ...

Firefox 66 released

Posted Mar 19, 2019 23:27 UTC (Tue) by roc (subscriber, #30627) [Link] (1 responses)

http://www.erahm.org/2019/03/13/doubling-the-number-of-co...

> Even on our worst-case-scenario stress test — AWSY which loads 100 pages in 30 tabs, repeated 3 times — we only saw a 6% increase in memory usage when turning on 8 content processes when compared to when we started the project.

Firefox 66 released

Posted Mar 22, 2019 9:30 UTC (Fri) by leromarinvit (subscriber, #56850) [Link]

Interesting to see what they consider a worst-case stress test (and, by extension, what would be considered typical usage). I guess I'm not a very typical user then, seeing as I currently have 47 tabs open - but only because I cleaned up most of my open tabs a few days ago. It's not uncommon for me to have several hundred...