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

Issue 713023 link

Starred by 2 users
Status: Duplicate
Merged: issue 713875
Owner: ----
Closed: Apr 2017
Cc:
█ sureshkumari@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome won't open until I kill a process

Reported by eldo...@gmail.com, Apr 19 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome Canary
2. 
3. 

What is the expected behavior?
Chrome start.

What went wrong?
Chrome doesn't start.

Did this work before? N/A 

Chrome version: 60.0.3074.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

Looking at the Windows task manager I can see 2 processes started:
- "C:\Users\...\AppData\Local\Google\Chrome SxS\Application\chrome.exe"
- "C:\Users\...\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --type=crashpad-handler /prefetch:7 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\...\AppData\Local\Google\Chrome SxS\User Data\Crashpad" "--metrics-dir=C:\Users\...\AppData\Local\Google\Chrome SxS\User Data" --url=https://clients2.google.com/cr/report --annotation=channel=canary --annotation=plat=Win64 --annotation=prod=Chrome --annotation=ver=60.0.3074.0 --initial-client-data=0x27c,0x280,0x284,0x278,0x288,0x7ff91b2419f8,0x7ff91b241a08,0x7ff91b2419d0

Killing the second one allows Chrome to open.

I tried to unistall, remove ChromeSxS folder and reinstall Chrome Canary, but the problem is still here.
I'm using Windows 10 and I have McAfee Endpoint Security 10.5, which unfortunately I cannot disable because it's enforced by my company policy.

Comment 1 by sureshkumari@chromium.org, Apr 21 2017

Cc: sureshkumari@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows-10,Windows-7,Mac-10.12.4 and Linux Ubuntu-14.04 using chrome stable version 58.0.3029.81 and canary 60.0.3076.0.
eldonzo@ could you please try again and let us know your observations if the issue still persists.

Thanks.

Comment 2 by eldo...@gmail.com, Apr 21 2017 

Today I'm not experiencing this issue with 60.0.3076.0, but it's happening with the stable version as soon as I updated it to 58.0.3029.81 (it used to work fine with 57.*).

Someone in my office reported the same issue with the stable version of Chrome.

If there is anything else I can provide you to help identifying the issue let me know.
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 21 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sureshkumari@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 4 by grt@chromium.org, Apr 21 2017

Components: -Internals>Installer Internals>PlatformIntegration
Regarding Chrome 58, this sounds like it might be  issue 713875 . With M58, Chrome launches after you kill some stranded chrome.exe processes?

Comment 5 by eldo...@gmail.com, Apr 21 2017 

Exactly, the command line of the process is similar to the one I reported in OP.

It happens also if I open a second window launching Chrome again while a first window is already open.

Now other people in my office are reporting the same issue.

Comment 6 by grt@chromium.org, Apr 21 2017

Mergedinto: 713875
Status: Duplicate (was: Unconfirmed)
Thanks. This does seem like the McAfee interaction being handled in  issue 713875 . I'll dup this into that one.
►

Sign in to add a comment