3 ms·

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

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" This has the annoying effect of turning every page into a crash symbol, but it's pretty easy to just refresh a whole row of tabs.

cookiecaper 9y ago
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-suspender/klbibkeccnjlkjkiokjodocebajanakg?hl=en 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.
- tagrun 9y ago
  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.