>Firefox sub-process allocates memory like a motherfucker for no reason>system freezes for like 5 minutes>finally unfreezes>kernel log indicates it OOM-killed some firefox processes (which is how I know)>now 12GB memory freeWhy is it like this?The Firefox process was named "Isolated Web Co". The cut-off name is due to retarded Linux reasons.
>>103235562Good God why don't you just use Windows imagine having to fuck around with Firefox what the fuck are you doing to yourself
>>103236284What else should I be using?
>>103235562is boycotting Brave really worth it?
>>103236401>brave shillEnd yourself with your half-assed chrome fork that is used only because it makes promises to low IQ schizos.
>>103236340Windows kek
>>103236340Ungoogled chromium
>>103235562>now 12GB memory freethat's impossible unless you had like 500 container tabs openuse bookmarks you fucking zoomer
>>103235562>Why is it like this?Because we let the web standard bloat well beyond its intended use-case, and now every web browser has to function effectively as a virtual machine for an operating system used to run applications as well as render text and embedded multimedia files.This is all Web 2.0's fault. We had perfectly usable and functional computers that were becoming increasingly user-friendly, but the entire tech industry decided that their end-users are all drooling retards who only know how to use a web browser, and then they made it true by decreeing that, in the name of user friendliness, everything must be a web application. And, like fools, we let them get away with it.
when kernel or systemd insists on not killing the process you can force trigger oom killer by pressing <alt + prtscrn + f>
>>103237124There was probably some more free before "it" happened. This just means it was trying to allocate at least 12 GB for absolutely nothing. The only thing I did was opening github.com, literally.
firefox has been hogging memory like crazy since the last few updoots. sometimes i get up to 8 gigs
>>103239602I have year long phases of firefox being good with memory changing with phases of firefox being bad at it.
ZRAM is a good way to mitigate system shitting the bed because of Firefox sudden RAM usage.-t. tab pro
