Live data from Hacker News

Multiprocess Firefox

developer.mozilla.org

1–10 of 171 posts

Re: Multiprocess Firefox

#2
Finally some movement on this! It really feels like an inferior experience in 2015 when your browser freezes from an unresponsive javascript in another tab.

Re: Multiprocess Firefox

#3
post #2

Finally some movement on this! It really feels like an inferior experience in 2015 when your browser freezes from an unresponsive javascript in another tab.

Currently, Firefox Nightly uses one process for the browser UI and a separate process for web content. However, one web content process is shared by all tabs. So slow JavaScript in one tab won't block the browser UI, but it will block web content in other tabs.

You can change this by increasing the "dom.ipc.processCount" preference in about:config, but there are still some known bugs with multiple content processes in desktop Firefox. There will be more work on multiple content processes in the future.

Re: Multiprocess Firefox

#7
Goodbye RAM :) Or better for RAM, since I can now selectively kill and resume processes?

Oh, I see it's not one process per tab. So does anyone know how I can more easily survive on 2GB with many tabs, other than by constantly killing processes?

Re: Multiprocess Firefox

#10
post #4

How much will process-per-tab increase memory usage?

This is multiprocess, but not process-per-tab. There is still a single rendering process for all tabs, at least for now.

But the ultimate plan seems to be to have process-per-tab. The article states: "In future iterations, we expect every browser tab to run in its own process."
Post reply on HN