277
Your Firefox should be doing this automatically when it detects the system needs more memory. You shouldn't need to do it manually in almost any case
Your OS should do this automatically, your programs shouldn't worry about cold memory.
Your OS can't decide when a tab is inactive though, given that they can run code, play media, etc. at arbitrary times.
Firefox can't either, because pretty much any page today will have JavaScript running.
The only way it works is to force tabs that haven't been opened in some time to unload regardless of activity... but that's something that the vast majority of users would not appreciate. For power users there are a ton of "tab unloader" add-ons that do this.
maybe @Eggymatrix ment swapping.
The OS tracks which memory-pages are used least and will swap them out when active programs need more ram than available.
Swapping anonymous pages is an extremely poor "solution" to cold memory. It's the big hammer approach that technically always works but isn't optimal for ...anything really. That's the best the kernel can easily and quickly know however which is why it's done at all.
It'd be much better if the process could shave off memory usage using its own domain knowledge. In the example of firefox, it's much faster and less jarring to the user to have 10 tabs reloaded from the web (browser shows a spinner as usual, doesn't lag) rather than swapped back in from disk (entire browser lags and it probably even takes longer).
There's no reliable mechanism to signal any of this to me knowledge however, so processes must guess the right time to do discard memory pre-emtively.
I believe you are mistaken, there is no way that reloading a tab from the web is faster than it being read from the disk.
For this you have to know that what gets swapped to disk is not the static content that you'd load upon opening a website, it's the entire memory used by the tab.
Static web content is usually kilobytes to megabytes and is also largely cached (on disk even). A tab's memory usage OTOH ranges from dozens to hundreds of MB.
Even a fast drive needs quite a long time (in computer terms) to load something like that, especially given that the access is likely not sequential and has a low queue depth.
Edge does this very aggressively and I hate it… Also I believe that Chromium based browsers use more memory per tab, so that might be the reason why it feels more aggressive. Firefox does this very rarely.
Nope! Not happening or at least not soon enough. Neither on macOS or Linux (can't speak for the stupid platform).
Firefox will happily keep tabs open, even if macOS reports major memory pressure or Linux needs to invoke the OOM killer because it's Gigabytes into swap.
Not to speak of what happens before memory pressure is reached; Firefox will also happily use all of your memory even if you'd rather have it free for something else you're going to do next.
Firefox does this automatically to prevent crashing. There's no real reason to unload tabs manually. If your operating system or Firefox needs more memory, then it will unload the tabs automatically. Unused ram is wasted ram. Don't be scared by ram usage going up, it gets freed on demand.
There are reasons, and there are addons that allow you to unload tabs via their right click menu.
For me it is a way to keep tabs in a window for organization without them using cpu. In some sense it's like replacing tabs with bookmarks that integrate into the browser like tabs.
I use this extension: https://addons.mozilla.org/en-US/firefox/addon/discard/ which provides an option in the context menu for tabs to discard them. I don't use it often but it can be helpful if your browser is slowing down.
I would like the opposite though. When I used chrome, my WhatsApp web tab would load even if I didn't open it, so I still got notifications. In Firefox I have to manually switch to that tab every time I open it.
I find pinning my WhatsApp tab sorts that out, it seems to autoload pinned tabs into memory on launch.
If this works, THANK YOU. It's been annoying me for so long.
EDIT: it does work.
"Auto tab discard" is the name of the add-on I use that also uses this functionality. Highly configurable for automatic discarding (based on total count for example), and also allows manually discarding with a click (or shortcut, I think).
use auto tab discard.
I use the addon Sideberry (for vertical tabs) and it brings the option to unload specific tabs with it's context menu.
I don't get why about:unloads doesn't let the user decide which specific tabs they want to close.
Hey thanks for sharing
I'm pretty sure that Chrome does this automatically. When I work I usually need about 98,000 tabs open at a time and often I don't actually click any of them but I need them.
Anyway I will often open a tab and have to wait to it for it to load. But I've played around with it and I don't seem to be able to get consistent results so I'm not sure what parameters it's using.
What the hell are you working?
Research :clueless:
Right now?
- Internal ticket tracker
- Internal knowledge base system
- OneNote with the actual knowledge base system because the knowledge base is never updated
- Corporate emails
- Client emails
- Spam messages blocking system
- Shift timetables
- Engineer to English random acronym guide. Unless you know what ROD means.
- O365 files
- O365 online Word document
- Software phone app
- YouTube
- PC parts picker website
- Steam website
- UPS live chat
- Lemme
So a fair few. Although I can probably close the UPS live chat tab because I'm getting nowhere with these idiots.
This reads like the dystopia in which every piece of software got replaces by a proprietary web application by some evil mega corp. What you need is at least a mail client and a word processor.
Firefox also does this automatically, and you're not supposed to mess with it.
No, no you don't. IF you aren't accessing stuff on them, you don't need them open. Keeping 100 tabs open for later, is stupid.
It also doesn't affect performance because Chrome closes them as needed so why not?
Where does it get unloaded to?
From what I understand it basically just saves the minimal state possible (URL, form inputs), which is lighter than keeping all the rendering details in memory, so maybe that minimal representation still stays in RAM as its footprint would be negligible.
It doesn’t save form inputs because when you click a suspended/unloaded tab, it reloads the whole page. Everything unsaved on that page is lost.
I really hope some day Firefox will work the way you say, though.
That's weird then, because this says:
The tab’s scroll position and form data are restored just like when the browser is restarted with the restore previous windows browser option.
If it doesn't do that then I'd say it's a bug?
It gets thrown away. When you go back to the tab it will effectively reload.
(It will attempt to save some extra information such as scroll position and form inputs but this isn't 100% reliable so I would treat it as a nice-to-have not something to rely on.)
/dev/null
But how else am I going to use up all 64GBs of ram?
Huge missed opportunity to name it Diet Tab...
this post was submitted on 06 Sep 2023
277 points (100.0% liked)
Firefox
17865 readers
6 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS