Re:The New Firefox and Ridiculous Numbers of Tabs
by sillysaurus3 on Friday July 21, 2017 @09:11PM
(#14824883)
I have a bash script called `kill-chrome-helpers` that kills all Chrome processes without terminating any Chrome windows. It kills extensions too, but whenever that happens Chrome pops up a bubble saying "click here to restore the extension", so usually I just run the script and then click a few times. The script is dead simple:
killall "Google Chrome Helper"
Re:The New Firefox and Ridiculous Numbers of Tabs
by cookiecaper on Saturday July 22, 2017 @12:28PM
(#14827932)
A couple things. First, it's best to avoid using `killall`. On Linux it searches the process list, but on Solaris and possibly other nixes, it kills all processes system-wide. Using `pkill` is a better habit, but read the manpage first because it matches a little differently.
Secondly, check out this extension for Chrome: https://chrome.google.com/webstore/detail/the-great-suspende... . It auto-suspends tabs that haven't been opened for a given time period (I think the default is 60 minutes). Can also whitelist domains, etc. I've been using it with great success for a long time now.
Re:The New Firefox and Ridiculous Numbers of Tabs
by tagrun on Saturday July 22, 2017 @02:13PM
(#14828493)
No, that is rather a Solaris quirk. That's ancient (literally) sysv behavior and killall in neither OpenBSD, nor FreeBSD work like that today.
So in practice, what you're saying isn't relevant to majority of *nix users today.
1. Open up Window->Task Manager
2. Sort by CPU
3. Tap back and forth between tab clusters with single digit+ CPU usage and the "End Process" button as they bubble to the top of the list
4. Try not to kill extensions
5. When I'm not seeing too many >1% processes, sort by memory usage
6. Kill everything over 99mb
7. Continue enjoying Chrome
Every time I do this little dance, I think: this would be much more fun as a little Space Invaders style video game. Wave 1 of enemies would be processes that bubble above 1%. Extensions would be friendlies. Wave 2 is high memory processes. It'd be fun to get a little score every time.
Of course, Chrome should just have a "use less resources" button that did all of that for you.