196

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 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

This 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).

Yeah procreation is sin. Masturbation is not.

You can, but i XXXXXXX can’t.

See.

Source: https://xenia.chimmie.k.vu/ (She has more art, I recommend checking it)

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.

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 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

Use all the RAM you want, but if another program needs it give it back ffs!

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.

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.)

fuck the fucking fuckers.

wat. lol. javascript has nothing to do with the memory consumption. just humans being shitty at their jobs.

Disagreed, memory Limiting definitely helps with over-consumption. Can't consume all the RAM when you only have access to 8GB of it.

*lynx (links are the things that tie the www together)

wait so you just lose tabs you haven't opened in X mins?

i have a tab sleeping extension & generally throttle the ram with opera

I tried that but I found that its effects on long term memory leakage weren't adequate for me, and it still consumed way too much RAM. Which is why I just decided to limit RAM for Firefox. It achieves a similar effect as the browser unloads tabs when it runs low on memory, it just doesn't wait until it's using 31GB of RAM and instead just uses up to 8GB (which is what I capped it at) before unloading tabs.