You can swear on the internet. Fuck, see?
You can, but i XXXXXXX can’t.
See.
One could also use w3m or links. All the RAM-hungry things (such as CSS3, JavaScript APIs and heavy multimedia files) will be finally gone for good.
*lynx (links are the things that tie the www together)
https://en.wikipedia.org/wiki/Links_(web_browser)
Best browser.
Minds are blown, thanks for the correction!
Sorry, the only solution is the web aborting JavaScript. never going to happen. trust me, i stand with richard stallman when it comes to javascript.
Disagreed, memory Limiting definitely helps with over-consumption. Can’t consume all the RAM when you only have access to 8GB of it.
wat. lol. javascript has nothing to do with the memory consumption. just humans being shitty at their jobs.
I will agree with you that VANILLA JavaScript isn’t to blame, but all the frameworks and packages are.
Yes, being shitty at their jobs. even the frameworks/packages are not to blame. its which you pick and how you use them.
for peoples context: just checked a few sites most range in the 30MB-150MB per page. which is pretty reasonable for the complexity of the websites involved. one included a streaming service actively playing a video.
Its just that these things add up across 100 tabs.
I work in tech, and I don’t understand people’s obsession with having all their RAM free at all times.
If you don’t use it, why do you have it?
Windows (not the best OS, but the one I know the most about), will lie to you about how much memory you have that’s free. It puts data in RAM as cache. In the event you need that data, it’s already loaded in RAM. Usually this is stuff like DLLs and executables for programs.
There’s a difference between “free” memory, and “available” memory.
In addition, RAM is always going down in price, so 32G today costs what 16G did, some number of years ago. The same can be said for 16G vs 8G, etc. Though, the comparison becomes less relevant as you get into much smaller and older memory types, since the cost per dimm will only ever go so low.
Buy the memory, use as much of it as you can, as often as you can. Go wild with it. Enjoy.
None of thaťs helpful. You know, when browser uses half your ram, teams quarter and rest of the programs the rest, windows is swapping on your SSD like a prick and you cannot switch windows - none of what you said helps. And of course, the RAM is soldered on and cannot be expanded.
I understand your point.
This is also why I don’t buy systems with soldered RAM. It’s a horrible trend in computer systems that RAM is soldered. It’s a lazy way to fix a problem and nobody should buy a system like that.
The industry needs to come up with better solutions.
There’s a difference between “free” memory, and “available” memory.
I agree with this, and I’m sure most people complaining about Firefox or Chrome’s abhorrent memory usage would too. The problem with most browsers is that they eat up the available memory and often do not give it back. So you end up with situations where you’re running low on available RAM even though you have 32GB installed.
Buy the memory, use as much of it as you can, as often as you can. Go wild with it. Enjoy.
Sure, if you release it when not using it, otherwise unlimited RAM privilege revoked. Memory leaks suck and when they chew up all your RAM and they continue to happen, offending apps should either be no longer used, or limited to their minimum necessary RAM requirements to limit the damage they’ll do.
Hence why I capped Firefox at 8GB, anything more would be wasted when it inevitably leaks.
Desktop file to limit Firefox to 8GB of RAM
[Desktop Entry] Version=1.0 Name=Firefox RAM limit 8GB GenericName=Firefox Ram limit 8GB Comment=Limit RAM for Firefox to 8GB; Exec=systemd-run --user --scope -p MemoryLimit=8G firefox Icon=firefox Type=Application Terminal=false Categories=Utility;Development; StartupWMClass=FirefoxI work in tech, and I don’t understand people’s obsession with having all their RAM free at all times.
If you don’t use it, why do you have it?
Windows (not the best OS, but the one I know the most about), will lie to you about how much memory you have that’s free. It puts data in RAM as cache. In the event you need that data, it’s already loaded in RAM. Usually this is stuff like DLLs and executables for programs.
There’s a difference between “free” memory, and “available” memory.
Linux and macOS do the same, although I wouldn’t call it lying per se :)
There is certainly a lack of understanding of the difference between free and available RAM. TLDR: yes, free RAM is indeed wasted RAM.
If you actually have a lot of free RAM, it’s probably because you either booted or freed a lot of RAM very recently. After using your computer for a while, most of your available RAM should not be free but rather being used for page cache and other caches.
After a program has just read and/or written more data from disk than will fit in available RAM, the kernel’s page cache (which is typically the bulk of that not-free-but-available memory) should be mostly populated by the most recent of those operations. This means that if that program (or any other program) reads those files again, before they are evicted from cache by other things, they will not need to wait for the disk and will get them back much faster.
However, managing all of this is the kernel’s job, and the not-free-but-available RAM being used for page cache is not (in any OS, as far as I know, though I mostly know Linux) attributed to the program(s) responsible for putting things there.
So, when people are complaining about an application using 40% of their RAM it is not necessarily due to them misunderstanding free-vs-available RAM. The used number for an application does not include the portion of the system’s not-free-but-available RAM which the application is also responsible for occupying.
(If you want to know which programs and/or which files are responsible for occupying your page cache… on Linux at least, it is not really possible without instrumenting your kernel. The kernel is just tracking blocks. There several tools which will let you see which blocks of a given file are cached, but there isn’t a reverse mapping from blocks to files.)
Use all the RAM you want, but if another program needs it give it back ffs!
Browsers have a really hard time with the last part. Hence why I recommended limiting it to something more manageable, that way it doesn’t chew up everything available.
For me there are programs that “can acceptably use that much RAM” and those that it’s “unacceptable”, to me. what’s 20% to 40% of my gaming rig’s resources may be uncomfortably taxing and laggy for my laptop. Its okay to waste resources on my gaming rig but the laptop needs all it can get. I accept some software will not reasonably run on the laptop. My employer has stuck me on 10yo hardware before, running windows 10 pro + intrusive expensive antivirus and nobody is around to question why their computers are getting 5-15fps and locking up for a minute or two when you open chrome. It becomes normal. Any software is the host and/or backbone for other running software should focus on reducing it’s own resource usage for the sake of its children.
Hating furries is already really cringe, but even more so when you have an anime profile picture. At that point it feels hypocritical.
Since their profile picture is Komi Shouko from “Komi can’t communicate”, who is sometimes canonically portrayed with cat ears they are either joking or rejecting their true inner self.
I don’t hate furries, but some of them have…weird kinks. Not this though. who gives a fuck if someone wears a buttplug? buttplugs are hot af.
Me when I take a joke seriously.
deleted by creator
Why the fuck is fuckin censored hut stuff like tailplugs not xD, what a fuckin bull shit.
fuck the fucking fuckers.
6 gig of ram on a browser!? wtf people close your old tabs.
I got tired of cleaning them out so I stopped. Now I have an emotional attachment to my 200+ tabs on Firefox mobile 🥹
I have so many the counter turned to infinity lol
I don’t understand this. The only people i have seen with a boatload of tabs open are twitch streamers. I have like maybe 5 open MAX and that’s rare.
Exatcly do it correctly and use multiple browsers each for a very specific type of work/thing you do you animals.
counterpoint: why does it need to keep the tabs in ram? either just discard the data and only keep the url, or if it would otherwise double check whether you want to close a tab then save things to disk cache after 5 minutes…
I still think the catgirl paws salute should be the new salute of the American Résistance.
I also think the catgirl paws salute should be recognized as a salute.
furryfox :3
Source: https://xenia.chimmie.k.vu/ (She has more art, I recommend checking it)
Would be cool if people actually used this as a replacement to their Firefox icon, or if there was a Firefox fork that used this itself for it.
asmongold would go on stream and start calling it woke.
I do!
And I found this guide to put it into the new tab page, though I haven’t tried to do so: https://this.squirrel.rocks/ff_newtab_logo
Really cool, though personally I would’ve resized the image slightly so that it would be the same size as the OG Firefox logo.
JUST BECAUSE I USE FIREFOX DOESN’T MEAN I’M A FURRY!
I mean, I am a furry.
BUT NOT BECAUSE I USE FIREFOX!
Bro has an anime profile pic and acts like he doesnt already have the tail plug in smh
Not only that, but the character in that profile pic often sprouts cat ears when she has strong feelings.
Hating furries is stage 1 of becoming a furry.
what if you don’t hate furries but don’t want to be one?
Ew! A Furry! ⬆
Soon the world shall be furries. And finally there will be peace on earth.
amen.
(although reasonably i think you might have too much faith in us. a society wide desire to be a colorful dog has the power to accomplish a great many things but peace on earth is a tall order)
Nah, I dont hate them. I don’t think I’d be enthusiastic about a full like mascot level fur suit during sex, but cat ears and tailplugs are adorable.
I haven’t heard somebody use the word “murring” in like a decade. Methinks they’re farther down the pipeline than they want to admit.
- The Internet is full of old memes that slowly make their way around to different communities and this could be one of them.
- What in the world is “murring”? This is the first time I’ve ever heard of it.
Stage 7 is memorizing the Macarena.
Stage 19 is affecting a québécois accent
Stage 42 is hitchhiking
Ben non?!
Mais non!
Already chossed the plug kind
🥴
I switched back to Firefox over a year ago and I have not noticed it using much less RAM than Chrome tbh. It’s definitely the better browser for all the other reasons, but I wouldn’t list memory utilization as a big advantage over other browsers
Most browsers these days have issues with high RAM usage, and memory leaks to. I’d recommend trying to limit the RAM of the browser, it stops it from eating up so much.
Here’s how I did it on linux. I’m sure there’s a way to do it if you’re on Windows though (might not be as good though).
Desktop file to limit Firefox to 8GB of RAM
[Desktop Entry] Version=1.0 Name=Firefox RAM limit 8GB GenericName=Firefox Ram limit 8GB Comment=Limit RAM for Firefox to 8GB; Exec=systemd-run --user --scope -p MemoryLimit=8G firefox Icon=firefox Type=Application Terminal=false Categories=Utility;Development; StartupWMClass=FirefoxThis is a script to limit Firefox to 8 gigabytes of RAM, you may change it lower or higher depending on what your needs are by changing the number from 8 to whatever else you’d like. Fair warning though setting it too low will cause Firefox to lag very badly, and will crash chromium browsers outright (Ask me how I found out).
The whole RAM thing is way overblown. Both browsers request a lot of RAM allocation, but only actually use a fraction of it. When the OS needs it for another process this “allocated, but unused” pool is the first to get used when “Free and unallocated” is gone
Problem is windows reports it all as the same in the task manager so people see that “70%” usage and freak out.
Tl:Dr Windows task manager is a fuckin lier.
the beta task manager vs gigachad HTOP
There’s also the idea that free RAM is somehow a good thing. In an ideal system, the RAM would always be “full” of potentially useful data. Having a bunch of empty RAM means that it’s not being useful. That space could be used to hold plenty of regularly used files that would be instantly loaded instead of having to pull from the drive again.
I don’t know when everyone started getting concerned with RAM usage, but in a perfect system, it would hold onto all of your frequently used programs and files that it could fit from boot and then those would load instantly.
Some Linux distros even allow loading the entire OS into RAM for wild speeds.
Idle RAM is just that. It does you no favors. Now, I do understand that you don’t want to be completely out, but we act like having 80% free is a goal for some reason.
Having programs steal or sit on RAM without using it is never a good thing. That’s why it’s called a memory leak, because it’s as if the free memory is leaking away. And it gets deprived from other apps that might need it more than Firefox or chromium does.
Your idea only works if programs actually take only as much ram as they need and give it back when done, but they don’t do that, they usually sit on it until it’s pried from their cold dead fingers. That’s what memory leaks are, and modern browsers these days are extremely prone to them.
Unused RAM is wasted RAM. It consumes the exact same amount of power whether there’s useful data in it or not. Any self-respecting operating system will fill up RAM that applications aren’t using with frequently accessed files, so they’re ready to go in an instant.
I think that’s precisely why limiting RAM on apps like Chrome or Firefox is so necessary, these apps never release their RAM when they are supposed to, they hoard anything that isn’t free and don’t give back when it’s needed, which is why in the reply to the top comment I shared a desktop entry to limit RAM on Firefox or whatever app you so choose.
Oh, I totally agree. Being afraid to call out to the allocator because “hey, I might need that memory later” is kinda not great. To a certain extent I can see how if an application tends to thrash memory, making a kajillion syscalls might hurt performance, enough that on many machines the gains from doing a single big allocation on the system and then slicing it up into small allocations in-process might outweigh the downsides, but still…
The problem is that the extra RAM used by a browser is held on an exclusive basis and so is not nicely reclaimable by the kernel. I love that Linux caches the shit out of files in RAM, it’s great. It’s also great that it can release that memory when I launch a chundering dumpster fire application that eats all of my RAM. If a browser had been holding that memory, then the godawful Linux OOM killer would have launched, halted all threads on the system, walked the entire process tree, and SIGKILLed something (probably not a browser tab) before letting everyone else resume.
With the way memory is currently managed, a bloated browser is a liability. Cached state needs to be stored in something like a
mmaped file so that the kernel can flush pages out of memory if someone else comes along with amalloc. Alternatively, there needs to be communication between a browser and a userspace OOM daemon. If the system started hitting a soft limit, then the browser could start unloading background shit more aggressively.Free memory is wasted memory, but so is memory that can’t be used for anything else when it’s needed.
Yeah, I agree. Browsers all seemed to act like they are the only thing running on the computer at some point, practically resembling their own OS with the amount of containerization and complexity. There should definitely be a way for the OS to request some RAM be released from the browser.
That’s why I just prefer to limit the RAM available to the browser to an amount that I feel is necessary for good performance while not so much that it causes issues with other things running. To some people that might sound like a bad or stupid idea but think of it this way. You just said that modern browsers are complex and resemble their own Operating System, right? Well if you were running a VM you probably wouldn’t give the virtualized OS complete access to all your RAM, that’s asking for the VM to crash or freeze your PC. So why should general practice be any different for a browser then, they may be less aggressive than a Kernel managed VM but they can still be problematic when they eat to much RAM. Which is why I choose to limit mine so it doesn’t get more than 8GB, which I feel is perfectly reasonable on most systems where that’s half of all the memory available, and even on bigger ones you’re not missing out on much. Firefox performs just as well with 8GB as it does with 16GB, but with 16GB it’ll eat way more than it uses.
Here’s the script I used. Should work for most linux users. I don’t know how to do it on Windows since I don’t use Browsers there for long enough periods for this to become problematic.\
Desktop file to limit Firefox to 8GB of RAM
[Desktop Entry] Version=1.0 Name=Firefox RAM limit 8GB GenericName=Firefox Ram limit 8GB Comment=Limit RAM for Firefox to 8GB; Exec=systemd-run --user --scope -p MemoryLimit=8G firefox Icon=firefox Type=Application Terminal=false Categories=Utility;Development; StartupWMClass=Firefox
Listen using Firefox doesn’t make me a furry.
I mean I am but that’s not why.
tailplug is fine but I draw the line at “fuckin”
Yeah procreation is sin. Masturbation is not.
