Chrome is unable to relaunch after update!
Reported by
abhinic...@gmail.com,
Mar 22 2017
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3046.0 Safari/537.36 Steps to reproduce the problem: 1. Updated the chrome by going to Help:About Google Chrome. 2. Message displayed after updation: Nearly up to date! Relaunch Google Chrome to finish updating. 3. Clicking on Relaunch button doesn't relaunch Chrome. 4. Going to Help:About Google still shows the same RELAUNCH button What is the expected behavior? It should relaunch after updating the chrome. What went wrong? Chrome window didn't relaunch after updation! Did this work before? N/A Chrome version: 59.0.3046.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0 This happens very often and after some time its just updated to more latest version and problem goes away!
,
Mar 23 2017
,
Mar 23 2017
does typing chrome://restart into the omnibox cause chrome to restart?
,
Mar 24 2017
I am not facing this issue after chrome updated to more latest version. I will have to check this when I face this issue again. Normally typing chrome://restart does work.
,
Mar 24 2017
Okay, please reply if it happens again. When it does happen, does clicking the Relaunch button in chrome://help do nothing at all, or does Chrome seem to take *some* steps toward restarting (such as closing some windows)?
,
Mar 24 2017
Normally I always first check to update chrome after opening the window but When fail to do so sometimes chromes shows at the "customize and control google chrome menu" to relaunch to get update. Kind of Like this: http://recesstec.com/wp-content/uploads/2015/05/Chrome-Update-2.jpg Sometimes chrome relaunch normally, other times it just closes the whole window and doesn't relaunch and If I again launch chrome, It still shows to relaunch chrome and doesn't get updated! I will try to use chrome://restart, when face this issue, and will report too.
,
Mar 24 2017
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
,
Mar 24 2017
Thanks. I look forward to hearing how chrome://restart fares the next time there is an update available.
,
Mar 29 2017
abhinickz6@ could you please let us know your observations after updating the canary to the latest versions. Thank You...
,
Mar 29 2017
So chrome has updated to this version: 59.0.3055.0 but still I didn't face this issue yet. I will update further if this happens again!!
,
Mar 29 2017
Thank you for providing more feedback. Adding requester "kkaluri@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
,
Mar 30 2017
As per comment#10,marking this issue as 'Wontfix'. Reporter, Please feel free to file a new issue when you find any. Thank you!!
,
Apr 18 2017
So I faced this issue again and chrome://restart doesn't work, I have to again open chrome from the shortcut. Version 60.0.3072.0 (Official Build) canary (64-bit). I have also attached an image which shows me to update Google chrome by relaunching.
,
Apr 21 2017
When relaunching results in all windows closing but Chrome not updating to the next version, would you please check Task Manager or Process Explorer to see if there are any lingering chrome.exe processes? Perhaps Chrome isn't completely shutting down during the restart, so it just opens up new windows in the old process. If you do find lingering chrome.exe procs, please report back the command line arguments for them. This will help figure out what is going on. Thanks.
,
Apr 21 2017
,
Apr 21 2017
Will do on facing this issue again.
,
Apr 21 2017
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
,
Apr 25 2017
This Time (Version 60.0.3078.0 (Official Build) canary (64-bit)) I clicked the relaunch button and also chrome://restart and both time I could see that some chrome processes were running in background (see attached picture), When I manually killed all the processes and open chrome It was already updated. Let me know If I need to do anything else for feedback.
,
Apr 26 2017
Thanks for that. It would help to know the command line arguments for the lingering processes. If you right-click on a column name in Task Manager and choose "Select columns", you can turn on the "Command Line" column.
,
Sep 7 2017
I've had this problem for a *long* time. I've always had to go into the Chrome folder (Windows 7 64-bit) and simply dump the chrome.exe and replace it with the newest version. I've attached my "debug.log" file from the Chrome folder. This has happened with every Chrome update.
,
Nov 13 2017
Thanks for the log file. It doesn't provide anything useful in this case. Do you find that there are lingering processes when you quit Chrome (see comment 14)?
,
Nov 14 2017
Yes, there are several remaining PIDs still active when I press the "RELAUNCH" button. Only one PID disappears and the remaining 5 don't close out. Oddly, when I launch Chrome, I get (6) chrome.exe PIDs. Then one will terminate. So I'm left with (5)... when I close Chrome they all terminate gracefully.
,
Nov 14 2017
Here is my command line: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --enable-native-gpu-memory-buffers --flag-switches-begin --enable-zero-copy --ignore-gpu-blacklist --enable-features=WebRTC-H264WithOpenH264FFmpeg --flag-switches-end
,
Dec 14 2017
Just FYI, in the previous update (not today) the issue for me has been resolved. My chrome browser is updating automatically and without issue.
,
Dec 15 2017
That's great. Thanks for letting us know. I wonder what was getting in the way before...
,
May 24 2018
As per comment #24, Closing this issue
,
May 24 2018
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by nyerramilli@chromium.org
, Mar 22 2017