196

16724 readers

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

765

firefox rule (slrpnk.net)

submitted 3 weeks ago by [email protected] to c/[email protected]

123 comments fedilink hide all child comments

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

[–] [email protected] 11 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

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.

[–] [email protected] 4 points 3 weeks ago* (last edited 3 weeks ago)

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