Pfft, everyone knows the cool kids use Lynx.
this post was submitted on 26 Nov 2024
752 points (97.6% liked)
196
16708 readers
2195 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 2 years ago
MODERATORS
What is the acceptable amount of ram a browser should be using? Is there a way of knowing how much is “wasted”? Is it even possible to waste ram, like what is wasted, time? Electricity?
Its being wasted if a memory leak causes it to use all 32 gigs of ram and crash
Even if it doesn't eat that much if it latches on to a portion of Memory and won't give it up unless killed that's still bad, and would be considered wasted as nothing else can use it for anything.
Empty ram is wasted ram. In theory the system should use whatever is available to cache and streamline.
load more comments
(1 replies)
If an app allocates it and ever uses it and refuses to give it up unless killed that can be considered wasted. It's called a memory leak and they can be really bad, especially when they consume a lot of memory, as that memory might as well be empty but is being held hostage by other apps.
If they released RAM then whatever amount they were using wouldn't be wasted and if more is needed they'd simply release it to free up resources. That hasn't been happening though, and most modern Browsers are notorious for consuming massive quantities without releasing it back to the pool.
In that case with the presence of Memory leaks being considered, and the fact that they continue to not be fixed, the acceptable amount of RAM a browser should be using (should even have access to) is the minimum necessary to run smoothly. From my testing with Firefox that seems to be 8GB. 4GB caused many websites to struggle. Such an arrangement ensures that even if a Browser begins eating RAM it won't eat up all the RAM and cause issues, worst that'll happen is that it itself will crash from eating all the 8GB it was allowed to access.
load more comments
(10 replies)
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.
wat. lol. javascript has nothing to do with the memory consumption. just humans being shitty at their jobs.
load more comments
(2 replies)
Disagreed, memory Limiting definitely helps with over-consumption. Can't consume all the RAM when you only have access to 8GB of it.
load more comments
(6 replies)
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.
byeah
I've been using the Firefox extension "Auto Tab Discard", which helps a lot with RAM usage. I like multi-tab-browsing and IME browsers just don't free up RAM when other applications need them.
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
It might be a bit of a misnomer. The tabs aren't deleted, just forcibly unloaded, and you can even prevent it from doing that on a per-tab-basis.
Yeah so it just means the tab's going to need to refresh when you click back to it. That seems perfect honestly, it's already what most phone browsers do more aggressively. Cheers :)
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.