Live data from Hacker News

Tab Unloading in Firefox 93

hacks.mozilla.org

221–230 of 283 posts

Re: Tab Unloading in Firefox 93

#221

Earlier quoted context omitted.

Right click for people with real mice

I have a real mouse. I didn't know that until yet! The long click has still the advantage that you don't need to click more than once: You can just hold the button, mouse-over the wanted entry, and than release the button triggering navigation to the history entry currently under the cursor.

[deleted]

Re: Tab Unloading in Firefox 93

#222

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…

That and the fact bookmark may ends up in a removed page, orphan link. Essentially people leave tabs open meant to keep a cache of it, maybe subconsciously. Bookmark doesn't do that. I don't mind maintaining it, so sometimes I use getpocket for that purpose but getpocket is not organized and frankly is not made for this purpose.

> That and the fact bookmark may ends up in a removed page, orphan link.

Except in the immediate short-term, keeping a tab open doesn't really fully help in that regard, though – even if the browser doesn't autonomously unloads tabs, sooner or later most people will eventually need to restart the browser and/or computer for updates, old pages are eventually evicted from the browser cache, and so tabs suffer from link rot just the same as bookmarks do.

Re: Tab Unloading in Firefox 93

#223

1. Just. Fucking. Unload. The. Tab. Already. I keep tabs around for context and reference. Lots of them. [1] 2. Preserve. User. State. I don't want the page to reload. I want what had been there to be restored. Page position, content, any inputs or adjustments I'd made. Not updated data, but previous state. 3. Do. Not. Lose. My. Shit. I can accomplish this far better myself than you will ever have need to do. 4. Any…

I can never understand people that have more than 10 tabs open :P When I reach that number I start closing. Seems to me just a waste of space and the whole tab bar is useless and messy (yes, I know about tab extensions). People should really get back to bookmarks, thats what they are for. Besides my usual bookmark folders, I have folders to hold temporary bookmarks (ToRead, ResearchSupport, etc...). These I know I wi…

1404 tabs open here.

Tab bar is indeed messy, I use Tree Style Tab in the side bar. And dozens of categorized windows, each with a name.

I don't need an alternative or better way. It works great and I hope this use case remains supported.

Re: Tab Unloading in Firefox 93

#224

It’s interesting to me that the lack of this feature has been one of the key differentiating features of browsers on desktop OSes compared to mobile browsers, such as Safari on iPads (and iPhones). It’s hard to do serious work on a mobile device that may silently unload a tab with unfinished work just because it was placed in background, whereas desktop browsers somewhat guaranteed that wouldn’t happen. In a way this…

This. Mobile devices are so utterly unsuited to actual productive use for this very reason. (I'm quite familiar with this, have attempted to use them in this manner for years, and am typing this on a Chrome/Android session I utterly despise.) The problem extends to other tools -- Termux, useful as it is, also randomly gets garbage collected and killed. Best I can understand, Android actually employs some AI-based mem…

It's even worse now that multi-process is a thing even on mobile, because it means that tabs get unloaded not just when the browser feels like it (practical quality of actual implementations might vary, but at least in theory the browser should know which tabs have been recently used, which tabs might be playing audio, etc. and so make a somewhat reasonable attempt of prioritisation which tabs should get unloaded first), but also whenever the OS randomly decides that one of your child processes (containing a random set of tabs) should die.

From following the bug tracker this definitively seems to be a problem with Firefox now – I wonder how Chrome gets around that problem, though? Do they suffer from the same problem, have they found some neat workaround, or are they cheating and being specially whitelisted by the OS?

Re: Tab Unloading in Firefox 93

#225
post #149

Earlier quoted context omitted.

Back basically works like it always did on static sites. Blame the fashion for single-page apps and endless scrolling for it being broken.

No. Blame browsers for not being user-agents any more. Browsers can cache websites, but only if websites tell them to do so. Users are never asked ( there is no setting ). And since websites usually don't want to be cached (for too long) browsers have to reload them ( which takes time ). Thats the reason Back-buttons are slow. Thats ( one of ) the reason(s) everybody has 100+ tabs open. SPAs and infinite scroll are (…

Some infinite scroll-type pages consume ridiculous amounts of memory the further you scroll (and if the page disallows direct navigation to a point in history and you need to find something older that you didn't save a direct link for, you've got no choice but to scroll, and scroll, and scroll…), so limitless caching isn't quite the right answer, either…

Re: Tab Unloading in Firefox 93

#226

Unrelated, but how do I get Firefox / Iceraven Android to _not_ unload tabs? It's really annoying when I want to load article pages for offline reading then Firefox just decides it wants to load the page again in Airplane mode.

If you mean a current version (i.e. not 68 or earlier), then it's not really possible – both because I think there's no option to configure Firefox's tab unloading itself except by recompiling, but also because now that Firefox loads tabs in separate content process, those separate content processes are an easy prey for the OS low-memory killer. Even the most-agressive memory optimiser won't kill the current foreground app itself, but anything else including content processes for unused (from the OS point of view) tabs may be fair game, even if that doesn't actually improve the ultimate user experience...

If your phone is known for aggressive memory management (https://dontkillmyapp.com/), maybe exempting Firefox from its memory optimisations (if that's possible) might help a little, but no guarantees.

Re: Tab Unloading in Firefox 93

#227
post #84

Kudos to the devs who fixed it. In my c++ project I was trying for weeks to figure out how to release back to the OS the memory that my std::vector was occupying, only to find out that there is no straight forward way of achieving so.

Detecting low memory scenarios is surprisingly hard on desktop operating systems, but trivially simple on Android/iOS. Firefox for Android already made extensive use of this feature while desktop Firefox' available memory watcher underwent a lot of changes over the years before becoming fairly reliable.

Though unfortunately especially on Android some vendors are overly aggressive in signalling memory pressure, so while the API might be easier to use, the practical result still isn't really good, either, because now instead tabs get unloaded too often. (And the move to multi-process on Android has the unfortunate side-effect that a too-aggressive system OOM killer can now pick out individual content processes and randomly kill tabs without regards to any priority as to which tabs should be unloaded first.)

Re: Tab Unloading in Firefox 93

#228
Bit off-topic maybe but regarding tab unloading, I have established a pretty solid workflow that lets me keep my thousands of tabs ready at hand, while not bogging down my entire system and keeping me focused on whatever is relevant at the moment.

I use the Sidebery addon for Firefox, set auto-fold to off and unload folded tabs to on. When I'm working on something, I keep all the branches that I need open, and when I'm done with that particular topic, I fold the branch, the tabs get unloaded, and I have a pretty list of squished branches that I can expand and get back to if I so wish. And if I'm really done with one, I can easily bookmark it and put it do "deep storage." It took 15 years of using Firefox but I finally have a tab management system that I'm happy with.

Re: Tab Unloading in Firefox 93

#229

It’s interesting to me that the lack of this feature has been one of the key differentiating features of browsers on desktop OSes compared to mobile browsers, such as Safari on iPads (and iPhones). It’s hard to do serious work on a mobile device that may silently unload a tab with unfinished work just because it was placed in background, whereas desktop browsers somewhat guaranteed that wouldn’t happen. In a way this…

It might still happen in the future, but what's described in this post doesn't seem like it's breaking that guarantee: it will only unload tabs that would otherwise have crashed the entire browser, so in cases where that guarantee wouldn't hold already.

Re: Tab Unloading in Firefox 93

#230
post #223

Earlier quoted context omitted.

I can never understand people that have more than 10 tabs open :P When I reach that number I start closing. Seems to me just a waste of space and the whole tab bar is useless and messy (yes, I know about tab extensions). People should really get back to bookmarks, thats what they are for. Besides my usual bookmark folders, I have folders to hold temporary bookmarks (ToRead, ResearchSupport, etc...). These I know I wi…

1404 tabs open here. Tab bar is indeed messy, I use Tree Style Tab in the side bar. And dozens of categorized windows, each with a name. I don't need an alternative or better way. It works great and I hope this use case remains supported.

I'd be fascinated to hear how it works in practice to have that many tabs active? Are you able to digest them in any reasonable fashion or even find content later on when you need it?

I can't relate to that amount of tabs, but do have an upper limit of around 100 at which time I start actively trimming them down (either dismiss as having lost importance, digest or bookmark for later digestion).

My bookmarks steadily grow, but are categorized, tagged and labelled in such a way that I can easily find and digest certain types of urls later on when I feel ready for it. They do grow faster then I can consume them though.

Post reply on HN