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

Issue 805872 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Feature



Sign in to add a comment

Not rebooting/updating properly when multiple browser processes are running

Reported by hoernl...@gmail.com, Jan 25 2018

Issue description

<b>Chrome Version: <From about:version: Google Chrome x.x.x.x></b>
<b>Chrome OS Version: <From about:version: Platform x.x.x.x></b>
<b>Chrome OS Platform: <Make/model of computer running Chrome OS></b>
<b>Network info: <network, encryption type, router model (if known)></b>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) have multiple profiles
(2) open browser windows with different profiles
(3) when update is ready, go to chrome://settings/help, click install and afterwards "restart to update" or something

Expected Result:
chrome should close, reopen all windows and show in chrome://settings/help that the new version is installed

Actual Result:
chrome closes, reopens all windows but in chrome://settings/help the "restart to update" or something text is displayed

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
don't know, but it happened right now multiple times with the update to Version 64.0.3282.119

What is the impact to the user, and is there a workaround? If so, what is
it?
can't update, but if you close all windows of all other profiles and then click restart, then it works (I wanted to save my work on other desktops and saw the open window of my clean dev profile which seemed to not have been closed, then I closed it and retried the restart/update and it worked)

 

Comment 1 by hoernl...@gmail.com, Jan 25 2018

update:

OS Version: Windows 7 Enterprise 64 bit
Chrome Version: happened with the latest 63.x

Labels: -OS-Chrome mp-triage OS-Windows
Labels: Needs-Triage-M63
Unable to reproduce the issue on chrome reported version 64.0.3282.119 using Windows-7 withe steps mentioned below:
1) Launched chrome reported version and created four profiles
2) Navigated to chrome://settings/help and clicked on relaunch when update is ready
3) Chromed got relaunched successfully and all profiles got opened and on chrome://settings/help page it shows "Google Chrome is up to date"

@Reporter:
Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue.

Thanks!
805872.mp4
2.1 MB View Download
Cc: viswatej...@techmahindra.com
Labels: Triaged-ET Needs-Feedback

Comment 6 by hoernl...@gmail.com, Jan 30 2018

Your setup matches mine, so it's a mystery. I'll just try again with the next update, if it happens again then I'll record a screencast and report back.
Project Member

Comment 7 by sheriffbot@chromium.org, Jan 30 2018

Cc: sc00335...@techmahindra.com
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@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
Labels: Needs-Feedback
As per comment #6, adding the Needs-Feedback label.

Thanks...!!

Comment 9 by hoernl...@gmail.com, Feb 26 2018

So it happened again, this time with video proof. On the left you see my "normal" chrome with me logged in, on the right side the test (dev) profile. If I click restart in my normal session the dev browser window does not close. The update takes ages because the ~50 tabs in my normal chrome session needed to reload ;-)
Unbenannt.mp4
994 KB View Download
Project Member

Comment 10 by sheriffbot@chromium.org, Feb 26 2018

Cc: krajshree@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 12 by grt@chromium.org, Apr 10 2018

Labels: Needs-Feedback
Hi. Are you using "--user-data-dir" to run two instances of chrome.exe with different User Data directories?
I'm not sure what WebStorm does with the second setting, the first one uses profile-directory.
627_20180410112159_Chrome Settings.png
33.7 KB View Download
Project Member

Comment 14 by sheriffbot@chromium.org, Apr 10 2018

Cc: grt@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 15 by grt@chromium.org, Apr 10 2018

Summary: Not rebooting/updating properly when multiple browser processes are running (was: Not rebooting/updating properly when multiple profiles open)
The "Use custom user data directory" option leads me to believe that this is using --user-data-dir=SOME_PATH when launching the browser. This is the source of your problems. When this switch is used to run multiple browser processes, all such processes must be shut down in order for a pending update to be applied. Running multiple browser processes with the same version of Chrome like this via --user-data-dir is not supported as an end-user feature because of edge cases such as this.

Could you use a different channel (https://www.chromium.org/getting-involved/dev-channel) to run multiple browsers rather than try to run stable Chrome with --user-data-dir? Beta, dev, and canary channels each install into a different location on disk and will use a distinct location for their user data.
Labels: -Type-Bug -Needs-Triage-M63 Type-Feature
Status: Available (was: Unconfirmed)
Per #15, moving this to a feature request.

Sign in to add a comment