On Sun, 27 Oct 2024 at 10:28, D. Hugh Redelmeier via talk <talk@gtalug.org> wrote:
From: Daniel Wayne Armstrong via talk <talk@gtalug.org>
I find this setting in Firefox's "about:config" to be useful for performance... When opening the browser, only load the contents of a pinned tab when I take a look at it; by default its set to "false" and I set it to "true":
browser.sessionstore.restore_pinned_tabs_on_demand
Interesting.
I didn't even know about pinned tabs. So this setting won't affect me.
Now that I know about pinned tabs, I have to think about how I'd use them. So far, I'm coming up empty (after 1 minute of thought).
Can anyone pipe up about how and why they use pinned tabs?
I already have browser.sessionstore.restore_on_demand false
I've found "about:performance" to be reasonably effective at finding the hog tabs. But then, I generally only have about 25-30 tabs open. Sorry it hasn't worked for you. I use pinned tabs heavily: I have about 15 sites I reference so commonly there seems no point in closing them, and they're easy to identify by the site icon so pinning them and reducing the tab size is a good idea. For example: three mail accounts, two calendars, a remote file browser/site, GitHub, etc. Something else I've noticed related to performance: on this machine, Gmail has never been a serious problem, but on another host (with similar memory and CPU) my Gmail tab would occasionally wind up the CPU like mad. My guess at the time (in no way proved) was that Gmail didn't like to be ignored for days or weeks, and wanted to fry your computer like a child throwing a tantrum to get attention. :-) Alvin was inclined to blame badly written JS hogging resources, and I'm in agreement. As the authors of that JS code are likely working on massive workstations where the browser is restarted frequently (because they're developers), they're unlikely to ever encounter the problems us plebs run into. -- Giles https://www.gilesorr.com/ gilesorr@gmail.com