New issue
Advanced search Search tips

Issue 721799 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 713875
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Launch unsuccessful until first spawned subprocess killed/probed

Reported by ha...@merrimack.edu, May 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome
2. 
3. 

What is the expected behavior?
Chrome application window appears

What went wrong?
Chrome window does not appear

Did this work before? Yes 57

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

After launching Chrome the application window does not appear. If I fire up Sysinternals Process Explorer in tree view I can see one Chrome.exe process that has one subprocess. The subprocess command line is:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=crashpad-handler /prefetch:7 "--database=C:\Users\hallr\AppData\Local\Google\Chrome\User Data\Crashpad" "--metrics-dir=C:\Users\hallr\AppData\Local\Google\Chrome\User Data" --url=https://clients2.google.com/cr/report --annotation=channel= --annotation=plat=Win32 --annotation=prod=Chrome --annotation=ver=58.0.3029.110 --initial-client-data=0x154,0x158,0x15c,0x150,0x160,0x6a967dec,0x6a967dfc,0x6a967dd0

Killing that subprocess seems to allow application startup to proceed--the Chrome application window instantly appears and things appear to work as expected.

You don't even need to actually kill that subprocess to get the desired results. If you look at Properties->Threads for that subprocess with ProcExp it terminates/crashes and the application window appears.
 
Labels: Needs-Triage-M58

Comment 2 by hdodda@chromium.org, May 15 2017

Components: Internals>Installer
unable to reproduce the issue using chrome stable M58 #58.0.3029.110 , routing it to the respective team for further triaging .

Thanks!

Comment 3 by grt@chromium.org, May 29 2017

Labels: Needs-Feedback
This sounds a bit like  issue 713875 , which was caused by McAfee DLP and has since been fixed by McAfee. Is this still happening for you?

Comment 4 by ha...@merrimack.edu, May 30 2017

Thanks, grt! McAfee DLP was definitely causing the issue. Works great now.
Project Member

Comment 5 by sheriffbot@chromium.org, May 30 2017

Cc: grt@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "grt@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 6 by grt@chromium.org, May 31 2017

Mergedinto: 713875
Status: Duplicate (was: Unconfirmed)
Super. Duping this into the existing issue.

Sign in to add a comment