4 ms·
That is... puzzling. I use Firefox on a 2GB Thinkpad T42p, regularly have 100+ tabs 'open' (as in 'opened in the background' which means it'll start rendering w
by Yetanfou 7y ago
That is... puzzling. I use Firefox on a 2GB Thinkpad T42p, regularly have 100+ tabs 'open' (as in 'opened in the background' which means it'll start rendering when I actually open the tab) over 2 or 3 active windows and I have never seen it being killed by the OOM killer. It can crawl due to paging but it does not get killed. To me this sounds like you should either add a bit of swap space or tune the OOM killer to be less trigger-happy.
- nvrspyx 7y agoIf they’re having OOM problems, especially with 32GB of RAM, I’d expect it to start thrashing the swap as it does mine on my Ubuntu box. As much as I like FF, it is not consistent across hardware/OS setups and I imagine it makes it rather difficult for Mozilla to debug as this has been an ongoing problem for years at this point.
- Yetanfou 7y agoMore likely there is no swap space defined so that any memory error will trigger the OOM killer.