5 ms·
I thought the strategy was always to to create a bunch of threads so it’s very opaque what chrome is actually using. That is to say, I’ve only seen chrome get
by theabacus 8y ago
I thought the strategy was always to to create a bunch of threads so it’s very opaque what chrome is actually using.
That is to say, I’ve only seen chrome get worse in this regard.
- alyandon 8y agoI had to recently increase my user noproc ulimit because Chrome was spawning so many background threads that it was hitting the limit and causing all my applications to crash/behave strangely. On a system with (only) 4GB of ram, Chrome is such a resource hog that it is almost unusable without Tab Suspender.
- kingbirdy 8y agoWhy not use a more lightweight browser then?
- alyandon 8y agoI generally use Firefox as my main browser. However, I've been leaning on Chrome while the whole post-XUL extension apocalypse settles down and session managers in Firefox are back on par to what they were prior to the switch to web extensions.
- majewsky 8y ago> while the whole post-XUL extension apocalypse settles down It hasn't settled yet? I'm not missing anything in my Firefox (but I don't know about session manager addons since I don't use any).
- newscracker 8y agoI very much miss Session Manager (from Mozdev) on newer Firefox releases. The WebExtensions based session management extensions are still not as rich or as reliable as that one. So on machines I control, I use an older version of Firefox so that I can rely on Session Manager and a few other extensions from the XUL world. Firefox 52.x ESR, which does work with XUL extensions, would remain a supported choice until September 2018 (a couple of more months from now). After that, there wouldn't be a Mozilla supported browser that's not exclusively WebExtensions based, AFAIK.