8 ms·
I think it's the specific pages - some Javascript is much more memory hungry that others. A few hundred HN or Wikipedia tabs work absolutely fine, I've tested.
by theamk 14d ago
I think it's the specific pages - some Javascript is much more memory hungry that others.
A few hundred HN or Wikipedia tabs work absolutely fine, I've tested. But there are much heavier sites, and only a few of those can cause the machine to start swapping until OOM, especially when left to work in the background.
(And unlike Chrome, Firefox does not seem to throttle/unload background tabs automatically... or if it does, it does it much less aggressively)
- gitaarik 13d agoYeah, that's it probably, I also notice that when I have certain pages open in tabs on the background, my Framework laptop fans start spinning faster, probably because of JS running on those sites. I don't know whether that wouldn't happen with Chrome, but yeah, if that's the case, then Chrome would have to reload / restore those pages and on Firefox they're still in memory. I rather just close those resource heavy pages, fortunately they're usally not the kinds of pages I need to use too often.