Uninstalling Chrome Stable on Windows kills running Chrome Canary processes |
||
Issue descriptionWhat steps will reproduce the problem? (1) On Windows, install 64.x Stable and 66.x Canary (2) Start 66.x Canary (3) Go to Windows Control Panel > Programs > Programs and Features (4) Uninstall Chrome 64.x Stable What is the expected result? 66.x Canary continues running. What happens instead? 66.x Canary gets killed.
,
Feb 22 2018
With the possibility of Chrome running as a service process (chrome/service, not Mojo service) for the Cloud Print Proxy, one would want to do "killall chrome" to clean up on uninstall. Though instead of killing all the chrome.exe processes, only kill the ones whose executable path match the path of the one being uninstalled.
,
Feb 22 2018
This is CloseAllChromeProcesses() in chrome/installer/setup/uninstall.cc. That code looks old... possibly written before SxS installers existed?
,
Feb 28 2018
This mostly happens when the stable being uninstalled is from an enterprise (.msi) installer, as --force-uninstall is always used in those cases. Yes, it would be much nicer to only kill chromen in the relevant install directory.
,
Aug 23
BTW: issue 876640 makes this behavior likely for any build with DCHECKs enabled (developer builds and/or Albatross builds). I'm working on a fix for that. |
||
►
Sign in to add a comment |
||
Comment 1 by robliao@chromium.org
, Feb 22 2018Status: Assigned (was: Untriaged)