Smart mode

[sindresorhus]

Currently there's a lot of useless processes in interactive mode that I would never care to close. Like all the Chrome helper processes. These makes it harder to find processes I actually want to close. With some simple heuristics I think we could hide away most of those useless processes.

Should smart mode be default when using the interactive UI?

What processes needs hiding?

• Google Chrome Helper (done)
• 2BUA8C4S2C.com.agilebits.onepassword-osx-helper
• -zsh

There is a $40.00 open bounty on this issue. Add more on Issuehunt.

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[sindresorhus]

Maybe we could group processes with the same name into one? And when selected, it would open a menu with an option to kill all or select individual processes.

[ishanjain28]

I think I found something that can help but It'll probably need some changes in ps-list.

Chrome creates a seperate process for every tab and extension and all these processes run with some options as shown in image. But it also starts one process that runs without any options and killing this process closes Google Chrome Completely.

I was thinking that may be we can modify the ps-list a bit and send another parameter in response that contains the arguments of a process. And then in fkill we can remove all chrome processes that were started with some argument and only show the ones that weren't started with an argument.

If the user kills this process it'll close chrome and it'll not show 50 chrome processes and close the window associated with that process.

[sindresorhus]

I was thinking that may be we can modify the ps-list a bit and send another parameter in response that contains the arguments of a process.

ps-list already returns that.

And then in fkill we can remove all chrome processes that were started with some argument and only show the ones that weren't started with an argument.

It's possible for users to start Chrome with arguments, like specifying where to put the profile data or open Incognito directly, so that wouldn't work, but I guess we could easily special case Chrome and detect its helper processes and hide them.

[sindresorhus]

but I guess we could easily special case Chrome and detect its helper processes and hide them.

This is done in 3.5.0. It now hides any helper processes.

[IssueHuntBot]

@issuehunt has funded $40.00 to this issue. See it on IssueHunt

[stroncium]

What is the status of this issue?

[sindresorhus]

@stroncium The following needs to be resolved: https://github.com/sindresorhus/fkill-cli/issues/6#issuecomment-282637495

Having a sub-menu for identically named processes would also let us add an entry to delete all processes with the same name.