3 ms·
I often do this with OS X Chrome: killall -9 -m "Chrome Helper" It kills all Chrome tab renderers, but you can easily reload them where you left off. Ultima
by vardump 11y ago
I often do this with OS X Chrome:
killall -9 -m "Chrome Helper"
It kills all Chrome tab renderers, but you can easily reload them where you left off. Ultimate battery saver.
Chrome seems to even remember textarea / input contents.
Edit: Not that I've ever had any issues with that simple killall, however the following might be safer, it tries to match the process path, name and "--renderer" command line parameter:
pkill -9 -f "Google Chrome\.app/.*/MacOS/Google Chrome Helper .*--type=renderer"
- SeanDav 11y agoIs there a Windows equivalent process?
- vardump 11y agoWell, this is a bit hackish, but I got this to work with a minute of effort: wmic Path win32_process Where "CommandLine Like '%chrome.exe\" --type=renderer%'" Call Terminate Tried it on Windows 10, latest Chrome. Ctrl-r didn't work on those killed tabs, had to click reload button. But other than that, the effect seemed to be same than on OS X. Use at your own risk. You can't use taskkill, because on Windows, all Chrome processes have the same file name, chrome.exe. Edit: This one should be a bit more reliable and safer. Note that it is not completely visible because of HN CSS: wmic Path win32_process Where "CommandLine Like '%--type=renderer%' and Name='chrome.exe'" Call Terminate
- lukifer 11y agoThanks for the tip! I frequently prune task processes manually, and I didn't know that killing all helper processes was safe to do. :D