4 ms·
Perhaps if web browsers in general returned to that crazy, old idea that ram is not an infinite resource and that I as a user should be able to set a reasonable
by alyandon 4y ago
Perhaps if web browsers in general returned to that crazy, old idea that ram is not an infinite resource and that I as a user should be able to set a reasonable limit on the maximum amount of ram a single web page or extension should be allowed to consume this wouldn't be a problem.
Instead, a few errant lines of javascript on a web page or in an extension is all that is needed to cause a web browser to consume every byte of available ram on a system and drive it into swap. :-/
I really miss the 90s web sometimes.
- hedora 4y agoThe person posting the bug says their 32GB machine has 10's of GB free. Later, someone points out the systemd-oom's oomctl is counting FS cache as "used". (Search the reddit thread for 'free -h'.) It sounds like the issue can be easily avoided by ensuring that the size of your FS + the memory you're running applications are using never exceeds 60% of usable RAM. I had to check to make sure this wasn't posted on April 1st. systemd is glorious, but I'm happily using a 90's-era init, FWIW.
- alyandon 4y agoSounds like they are using cgroups to enforce memory limits then? I seem to recall that being a problem with containers getting killed as well because FS cache counts against their memory limit.
- outime 4y agoThe 90s web that loaded an ActiveX which would automatically screw up your whole computer? Popups with ads that move around and cannot be closed? BSOD after entering the wrong website? Half of the browser window filled with toolbars? It seems that rose-colored glasses are very present here.
- alyandon 4y agoNot at all rose colored, I merely... avoided surfing sites that did that?