Live data from Hacker News

Tab Unloading in Firefox 93

hacks.mozilla.org

111–120 of 283 posts

Re: Tab Unloading in Firefox 93

#111
post #65

Earlier quoted context omitted.

Bookmarking systems are completely outdated, but I'm not sure what they should be replaced with. What would help you in this case so you didn't have to worry about losing the tabs if you closed them?

Maybe a sufficiently good implementation of history search could replace the need for bookmarks entirely. Instead of just matching on page titles, match on content as well. Rank results according to relevance and time spent on the page. Or alternately, maybe bookmarks could become an extension of existing tab management features. Something like Chrome's tab groups or the Tree Style Tabs[1] extension for Firefox, but…

Safari's history search has been able to search content for a probably decade now.

Re: Tab Unloading in Firefox 93

#112
post #13

I've never had Firefox crash. I guess they are reaching for those edge cases on power users who keep a billion tabs open. Maybe I'm missing some sort of productivity hack that involves leaving 100+ tabs open.

Firefox crashes completely at least once a week for me, and tabs crash at least once a day. I had a brand new tab crash the other day, just seconds after I had opened it and visited a text-only site (no JS, no images). I'm running Firefox 92 on up to date Debian on a machine with 64GB of memory; it's not running out of RAM.

I still use it because it's better than Chrome, and I wouldn't touch Brave with a 10 foot pole.

Re: Tab Unloading in Firefox 93

#113
post #104

Earlier quoted context omitted.

I'm going to reply with a comment stolen from a different HN discussion: The fact that people (myself included) have 100s of tabs open is a symptom of just how broken bookmarking is on the modern web. Bookmarks are a miserable way to create a placeholder for your thoughts. It's too static, must be maintained, and generally prone to link rot. I'm a scientist. I open and read 10-20-100 links for a given topic depending…

It sounds like you could just close these tabs once you switch to another one, or maybe have a timer on them so that they auto-close after N hours. There are probably extensions for that. I use very few bookmarks now, the ones I have are just for websites that may be hard to find, or simply the ones that I visit enough to want a quick suggestion when I start typing the URL. I almost never regret closing a tab, if I n…

Auto discard + tree style tabs = no reason to actually close tabs.

Re: Tab Unloading in Firefox 93

#114
post #22

What I want implemented.. Chrome/Firefox whatever... is that instead of unloading and reloading when I go back to the tab I want it to export basically an HTML file and when I click back to that tab, I want it to reload the HTML file instead with some notification/marker that it is a "cached" version. There are times where I'll leave a tab in the background that I don't want refreshed but when it gets unloaded, poof,…

SingleFile [1] is supposed to be able to do that (more or less) by enabling these settings in the options page:

- User Interface > open saved page in a new tab

- User Interface > auto-close the tab after the page is saved

- Auto-save > auto-save on tab discard

Then you have to select in the context menu of the extension: Auto-save > Auto-save all tabs (or Auto-save unpinned tabs)

[1] https://github.com/gildas-lormeau/SingleFile

Re: Tab Unloading in Firefox 93

#115
post #77
post #22

What I want implemented.. Chrome/Firefox whatever... is that instead of unloading and reloading when I go back to the tab I want it to export basically an HTML file and when I click back to that tab, I want it to reload the HTML file instead with some notification/marker that it is a "cached" version. There are times where I'll leave a tab in the background that I don't want refreshed but when it gets unloaded, poof,…

I was surprised recently to learn about the back/forward cache (bfcache) [1], a common browser optimization that sort of does what you're describing but stores a more complete snapshot of the page, including the JS heap. I'm not sure if it's used in this new FF feature (the article doesn't give details about the mechanism of unloading). However the bfcache unsurprisingly causes edge cases in JS-heavy pages/SPAs, and…

Only recently when I flew backwards through about 50 history steps (entirely different webpages) on my phone did I think more deeply about how impressive it was that it was so seamless.

Re: Tab Unloading in Firefox 93

#116
post #13

I've never had Firefox crash. I guess they are reaching for those edge cases on power users who keep a billion tabs open. Maybe I'm missing some sort of productivity hack that involves leaving 100+ tabs open.

How is that possible, I get FF crashes literally every time I load a moderately intensive website (eg. Google Keep). I still use FF because I can't abide Chrome. My PC is admittedly a bit older (only 6 gigs RAM) but still.

You should really check if you have bad memory. I've found firefox to be very sensitive to such an issue

Re: Tab Unloading in Firefox 93

#117
post #13

I've never had Firefox crash. I guess they are reaching for those edge cases on power users who keep a billion tabs open. Maybe I'm missing some sort of productivity hack that involves leaving 100+ tabs open.

I'm going to reply with a comment stolen from a different HN discussion: The fact that people (myself included) have 100s of tabs open is a symptom of just how broken bookmarking is on the modern web. Bookmarks are a miserable way to create a placeholder for your thoughts. It's too static, must be maintained, and generally prone to link rot. I'm a scientist. I open and read 10-20-100 links for a given topic depending…

It's more of a symptom, how bloated the modern web is.

5+ browser windows on 32mb of ram was never an issue back in the win95 time (so, whole os + browser and 5 pages). Now, we've got 8 gb of ram as pretty much minimum on mid range laptops, soon even on phones (flagships have it now), and browsers have become a biggest memory user (outside of newish games) on an average pc.

Re: Tab Unloading in Firefox 93

#118
post #112
post #13

I've never had Firefox crash. I guess they are reaching for those edge cases on power users who keep a billion tabs open. Maybe I'm missing some sort of productivity hack that involves leaving 100+ tabs open.

Firefox crashes completely at least once a week for me, and tabs crash at least once a day. I had a brand new tab crash the other day, just seconds after I had opened it and visited a text-only site (no JS, no images). I'm running Firefox 92 on up to date Debian on a machine with 64GB of memory; it's not running out of RAM. I still use it because it's better than Chrome, and I wouldn't touch Brave with a 10 foot pole…

What add-ons do you have installed? I've never had a problem like this in Firefox, in the 10+ years it has been my primary browser (on Windows though). Have you done a memory test too? Something definitely sounds broken here.

Re: Tab Unloading in Firefox 93

#119

Earlier quoted context omitted.

I'm going to reply with a comment stolen from a different HN discussion: The fact that people (myself included) have 100s of tabs open is a symptom of just how broken bookmarking is on the modern web. Bookmarks are a miserable way to create a placeholder for your thoughts. It's too static, must be maintained, and generally prone to link rot. I'm a scientist. I open and read 10-20-100 links for a given topic depending…

It's more of a symptom, how bloated the modern web is. 5+ browser windows on 32mb of ram was never an issue back in the win95 time (so, whole os + browser and 5 pages). Now, we've got 8 gb of ram as pretty much minimum on mid range laptops, soon even on phones (flagships have it now), and browsers have become a biggest memory user (outside of newish games) on an average pc.

In 1995 there was no tabbing (I think?). I have 5+ browser windows with 100+ tabs open, so more like 500 browser windows, not 5.
Post reply on HN