196

16748 readers

2363 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 2 years ago

MODERATORS

[email protected]

767

firefox rule (slrpnk.net)

submitted 1 month ago by [email protected] to c/[email protected]

124 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

Somehow I don't really agree with that theory when Firefox was chomping down on 31.5GB of RAM and causing other things to crash or slow down (crashed Gnome shell a few times which was fun), as well as crashing often itself. When I limited the RAM to 8GB using the method outlined in my other comments all the mentioned issues went away. It would run smoothly, and old tabs would just unload, something which didn't happen before. And most of all, everything else ran smoothly without issues or hiccups.

Moral of the story, when apps leak RAM, limit their RAM. RAM held by apps and not being released is just as wasted as if it wasn't used at all, because chances are it isn't being used at all, and isn't able to be used.