Firefox: Process for each tab: How?
by rnturn from LinuxQuestions.org on (#4STN3)
I've read about browsers trying to keep an errant tab from bringing down the whole browser by running a separate process for each tab. Sounds like a good idea but how does someone actually turn that on for Firefox?
I've seen a few pages that claim to show how it's done for Firefox running on Windows but nothing that shows, specifically, how to do the same thing on Linux. I've toyed with the "Content per process" setting but it seems to have zero relationship to the number of processes/tab.
Is this "tab == process" feature Windows-only?
If so, is the best (or only) way to identify what tabs are pegging the CPU utilization via the Task Manager and the so-called "Energy impact"? Sometimes, browser performance is so-o-o sluggish it appears that it's hung and trying to open up the Task Manager might take a very long time.
I typically have htop(1) running in a virtual console to monitor who's taking over the CPU when I sense performance problems but see no means of tying Firefox PIDs to particular tabs so as to identify which process/tab to kill. Often, Firefox might be catatonic while the rest of the desktop is working just fine. Knowing what PID to clobber would be handy in those instances. Not being able to identify the culprit tab often means my best course of action is to "killall -9" everything Firefox-related and restoring the tabs when asked after restarting the browser and hoping the problem doesn't recur right away.
Surely there's a better way (besides returning to Chromium) or making the Task Manager my default page---so I don't have to wait quite so long to access it when performance goes south. (If that's even possible.)
Thoughts? Ideas?
TIA...
I've seen a few pages that claim to show how it's done for Firefox running on Windows but nothing that shows, specifically, how to do the same thing on Linux. I've toyed with the "Content per process" setting but it seems to have zero relationship to the number of processes/tab.
Is this "tab == process" feature Windows-only?
If so, is the best (or only) way to identify what tabs are pegging the CPU utilization via the Task Manager and the so-called "Energy impact"? Sometimes, browser performance is so-o-o sluggish it appears that it's hung and trying to open up the Task Manager might take a very long time.
I typically have htop(1) running in a virtual console to monitor who's taking over the CPU when I sense performance problems but see no means of tying Firefox PIDs to particular tabs so as to identify which process/tab to kill. Often, Firefox might be catatonic while the rest of the desktop is working just fine. Knowing what PID to clobber would be handy in those instances. Not being able to identify the culprit tab often means my best course of action is to "killall -9" everything Firefox-related and restoring the tabs when asked after restarting the browser and hoping the problem doesn't recur right away.
Surely there's a better way (besides returning to Chromium) or making the Task Manager my default page---so I don't have to wait quite so long to access it when performance goes south. (If that's even possible.)
Thoughts? Ideas?
TIA...