769
firefox rule
(slrpnk.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Nov 2024
769 points (97.5% liked)
196
17562 readers
371 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
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.