Unable to reproduce the issue on windows 7 using chrome version 58.0.3029.96.Able to launch chrome without any issues.

ncasagrande1@Could you please try the issue with latest stable  58.0.3029.96 and update the thread if the issue still persists.

Thanks,

Hi sorry none of those files in the zip contained anything useful I even deleted the file because it might contain some personal info as those were various profile related db logs.

Please look for the chrome_debug.log in the installation folder of Chrome (if chrome is installed per user it will be in <profile>\AppData\Local\Google\Chrome\Application (this is the only case this file will not be in the user data)

Also in the task manager use the menu to enable the "command line" column in the process list and stretch it as much as possible when taking a screenshot of the task manager. This way it will be visible which types are the two started processes.

Thanks.

Are you running in a Citrix environment? Do you have McAfee DLP or another AV running?

i am running in a citrix environment, but not with shared desktops, these are full clones windows 7 vm's, much like a physical desktop but all with the same image.  i am not running any av or mcafee dlp

logs attached and screen shot

Deleted: 222.jpg 192 KB

	222.jpg 192 KB View Download

Deleted: chrome_debug.log 387 KB

chrome_debug.log 387 KB View Download

Thank you for providing more feedback. Adding requester "kavvaru@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

It seems though the problem you observe is pretty much the same as when running Chrome in a XenApp session. Can you try to apply the config change from https://support.google.com/chrome/a/answer/7380899 and see if this fixes it.

i am not running in a xenapp environment on a server o/s.  this is running in windows 7 32 bit with virtual desktops which is much different, i don't even have that reg key on my system.  

Deleted: 222.jpg 46.6 KB

	222.jpg 46.6 KB View Download

This key is not there per default. It has to be added if needed. Please try putting it there and if this doesn't help it will be great if you could provide us with remote access to a test instance of your installation so that we can investigate. If this is needed please use pastarmovj at chromium.org to arrange the access and we will investigate.

@ncasagrande1-- Could you please respond to the comment #8 and update the thread .

#8   I worked with a google engineer on my issue, it is not related to the xenapp as mentioned above.  i do not run xenapp nor a server o/s so it did not apply to me.  he did determine this was due to the re-directed chrome profile and i was able to prove that, however there are other users who do not have a re-directed profile and the same issue is occurring, so i'm not sure this is exactly the solution.  pastarmovj@chromium.org is the engineer i am working with.  i've asked for an action plan to migrate users from the redirected profile to the google sync as stated in this article without data loss

https://support.google.com/chrome/a/answer/7349337?hl=en.

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

is there any update to this? I am also facing the same issue at work. I am using a laptop with Windows 7 Enterprise, 32-bit. I also have admin rights on my laptop, yet having the same issue of Chrome not starting and 2 processes getting created.
Chrome Version 58.0.3029.96

what is the resolution?

Re #13. Is your profile hosted on your local hard drive or on a network location?

julian was able to attribute my issue to the roaming profiles, however we've been doing those for years now and only with version 58 did this start causing issues.  there are plenty of others with this same issue so i definitely think there is a bug here google needs to investigate.  

Admittedly this has never been a supported configuration though. This is why Chrome greets you with this bubble that you are running unsupported config since over 3 years. :)

We are rather trying to offer viable alternatives that does not require us to compromise the security properties of the browser for example in the face of the feature described here https://support.google.com/chrome/a/answer/7349337 .

i see, thank you for that insight, i never realized it was un-supported.  

ncasagrande1@ could you please confirm shall we close this issue as per comment #17?

Thanks,

Hey,
I'd say we keep it open for now. I am still doing some investigation on the user's setup. I will take care of it once it is done :)

I am closing this bug now. The customer successfully deployed this feature.