3 ms·
Nevertheless, I prefer Chrome's approach. I can just open the process explorer and kill a few of the most memory hungry tabs/tab groups; with Firefox, there's n
by tomp 10y ago
Nevertheless, I prefer Chrome's approach. I can just open the process explorer and kill a few of the most memory hungry tabs/tab groups; with Firefox, there's no other solution than killing the whole browser.
Can't wait for this fix!
- NoGravitas 10y agoI believe in current Firefox you could kill the memory-hungry tabs, then go to about:memory and force a GC. Or restart and let your tabs stay open but not loaded until you use them. Not that either of these is super-convenient.
- rwmj 10y agoIn Firefox 47 (or 48?) you can now do: about:performance which displays/kills the CPU hungry tabs directly.