New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 787823 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Lingering process after quitting Chrome, won't re-open

Reported by cc...@wealthsimple.com, Nov 22 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome
2. Quit the application
3. Try to launch Chrome again
4. Chrome will not launch or open new browser windows.
5. Investigate Activity Monitor, see two lingering Chrome processes (not expected since I quit the application)
6. Kill the lingering Chrome processes (via: `kill PID`)
7. Launch Chrome with no issues.
8. Repeat

What is the expected behavior?
After quitting Chrome, I expect all processes to end, and for me to be able to re-launch the application with no issues.

What went wrong?
Chrome does not launch after quitting.

Did this work before? Yes Previous version before latest update.

Chrome version: 62.0.3202.94  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
Cc: shrike@chromium.org
Labels: Needs-Triage-M62
Cc: divya.pa...@techmahindra.com
Labels: Needs-Feedback Triaged-ET
Unable to reproduce the issue on reported version 62.0.3202.94 using Mac 10.12.6, could you please uninstall and reinstall latest stable from https://www.chromium.org/getting-involved/dev-channel

If the issue stills persists please provide your observation

[mac bug triage]

How are you quitting Chrome? Via Cmd+Q / Chrome -> Quit Google Chrome? Do you have any extensions or apps installed? Please try this on a new profile without any extensions and see if you can still reproduce the issue.

If yes, can you give a bit more information about which Chrome processes are still lingering in Activity Monitor and provide a sample? (Activity Monitor -> Cog icon -> Sample Process). Thanks.
Uninstalled and re-installed latest version. I haven't noticed this issue since I reported it. It seems to be occasionally after quitting Chrome via "Cmd+Q", or if Chrome "closes unexpectedly". I'm unsure how to recreate these exact conditions that cause it to behave abnormally. But I will continue to monitor and add details to this issue if I experience this again.
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 29 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by shrike@chromium.org, Nov 29 2017

> 5. Investigate Activity Monitor, see two lingering Chrome processes (not expected since I quit the application)

At this point had the black dot disappeared from beneath the Chrome app icon in the dock? Or was the black dot still there (indicating Chrome was still in the process of quitting)?
There was no black dot underneath the Chrome app icon on the dock. I also could not right click on the app icon to open up the menu (that usually would have the Force Quit option). Clicking on the app icon did nothing

Comment 8 by shrike@chromium.org, Nov 30 2017

Status: WontFix (was: Unconfirmed)
If the block dot was still there, Chrome had not fully shut down (so it's not surprising Activity Monitor listed some Chrome processes). If Chrome was taking forever to shut down that would be bad, but wouldn't be the same as this bug. Please file a bug if Chrome is hanging on quit.

There was _no_ black dot - so it appeared as if Chrome had fully shut down. (I think you misread my previous comment).
Status: Unconfirmed (was: WontFix)
Sorry, I did misread.

Comment 11 by sdy@chromium.org, Dec 6 2017

Labels: Needs-Feedback
Would you mind doing two things to collect more information?

- In a Terminal, run `pgrep -lf Chrome` while Chrome is in this state to see which processes exactly are still around. Post the results to the bug.

- In Activity Monitor, "sample" each leftover process. Save the samples and add them to the bug.
I can no longer reproduce this issue. So this bug can be closed for now - if I do run into it again, I will make sure to include the above requested information.
Project Member

Comment 13 by sheriffbot@chromium.org, Dec 6 2017

Cc: sdy@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sdy@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

Comment 14 by sdy@chromium.org, Dec 6 2017

Labels: Needs-Feedback
Status: WontFix (was: Unconfirmed)
Sounds like a plan!

Sign in to add a comment