Yes, about #1 issue. Is just a small change, as far as I know, the process is always called that. I have 2 pcs with linux and chromium and it works ok in both of them.

If the pc is executing chrome and chromium, it should kill the tabs of both browsers.

Ubuntu running Chrome 51.0.2704.63 (64-bit) The past few days I've noticed this is killing all my extensions as well as tabs.

Haven't used kill-tabs for a week or two - so I presume this has happened with the most recent Chrome (stable) update.

Curious if anyone else has experienced the same issue.

I have no idea what else could I write here :/ I have just realized after few npm & node updates that kill-tabs stopped working. It simply does nothing, none of tabs get's killed, no error, no message gets shown.

$ node --version
v4.2.2

$ npm --version
3.4.1

$ kill-tabs

$

I'm using Windows 8.1, and I have tried re-installing many times.

I'm using Chromium 43.0.2357.134 (64-bit). You need more info for debugging?

In the meantime, this line does the trick for me:

ps ax|sed -n -e '/chromium.*--type=renderer/ {/--extension-process/ !{s/^\([0-9]*\).*/\1/p}}'|xargs kill

❯ kill-tabs
(node:46518) Warning: process.on(SIGPROF) is reserved while debugging

❯ kill-tabs --version
2.1.0

❯ node -v
v8.6.0

❯ node -v #also tested on
v9.8.0

High Sierra 10.13.3

(feel free to use the image above as a screenshot; it's the result of killing ~100 tabs).

BTW, tab titles are still preserved, and you can look up any closed tab with the Tabs extension.

This is not really an issue, just a mention.

I have the same tendency to open a lot of tabs and in need of a solution to the resource hogging problem. Some time ago I have found this extension called The Great Suspender (github repo) and have been using it to great satisfaction.

One particular advantage over kill-tabs is that you don't have to kill all tabs at once. The granularity provided by the toolbar button is to either kill the current tab or all the tabs in the current window.

Hope it helps!

It seems there is a bug at line 11 of windows.js script.

The call from promisify(childProcess.exec) at line 9 will return an object with the following properties: stderr, stdout, error.

To be able succesffully call execall we need to access the stdout value.

I'm pushing a fix in a few minutes. I will also be a good idea to check for stderr and report accordingly.

I'm also a tab-abuser, but I prefer Edge. This PR adds Edge to the process list, the options and the README.

This is one of my first OSS PRs, so please let me know if I did anything wrong!

Hi @sindresorhus

First, thanks for this module! I use it almost daily both via cli as well as macOS shortcuts to help with memory/battery management.

I noticed that this wasn't killing tabs in Brave Browser. Did a bit of digging and it looks like at some point the process name was updated to 'Brave Browser Helper' on macOS. Unfortunately I don't have access to any other OS at the moment, so wasn't able to check if this issue is also present elsewhere.

Thanks 👋

type idea

issue I need many tabs opened and use only time to time - meanwhile they decreace performance - so I want kill just them, and my important still have active

solution create command-line option "except" • except-domain -- eg $ kill-tabs --except-domain google.com • except-title -- eg $ kill-tabs --except-title google

Figure out what the process name for tabs is on OS X, Linux and Windows and implement it here: https://github.com/sindresorhus/kill-tabs/commit/cb627bc2e9ca6bf236b12b85a81ed5dee266c2c9#diff-168726dbe96b3ce427e7fedce31bb0bcR5 and here https://github.com/sindresorhus/kill-tabs/commit/cb627bc2e9ca6bf236b12b85a81ed5dee266c2c9#diff-168726dbe96b3ce427e7fedce31bb0bcR30