Chrome Processes Remain after Chome Closes
Reported by
greg.and...@pearson.com,
Dec 19 2016
|
|||||
Issue description
Chrome Version : Version 54.0.2840.59 (64-bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: OK
Firefox: OK
IE: OK
What steps will reproduce the problem?
(1) Quit Chrome
(2) Check processes
(3)
What is the expected result? no "zombie" processes remain
What happens instead? Chrome processes remain
Please provide any additional information below. Attach a screenshot if
possible.
Our product has a SecureBrowser which will not start if applications are running. Even though Chrome.exe is quit, the browser will not start and will cite that chrome.exe is still running, even though it is not. With any questions, please feel free to reach out.
Thanks!
Greg
,
Jan 6 2017
Tested on Mac 10.12.2 using chrome M54 #54.0.2840.59 and issue is not reproduced. Attached screencast for reference. @greg.anderson-- Could you please check the attached screencast and confirm us if we had missed out anything in reproducing the issue . And also try with chrome latest stable and a fresh profile without any extensions , if you still able to reproduce the issue , write us ur observations. Thanks!
,
Nov 9 2017
Closing due to lack of feedback response that has been requested. If the issue still reproduces please open a new issue with the details requested.
,
Nov 9 2017
This still exists and is hurting our clientele!!
,
Nov 9 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 9 2017
If you have an extension or app with "permissions": ["background"] in manifest.json it will run even if Chrome is closed, which is a documented feature, and it can be disabled in browser settings: "Continue running background apps when Google Chrome is closed".
,
Jan 9 2018
@Reporter: Could you please check the issue as per comment#6 and let us know the behaviour. And also please upgrade to latest build and check the issue. This would help in further triaging of the issue Thanks!
,
Jun 11 2018
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Dec 20 2016