Provide some help to users for whom the rename dance consistently fails |
|||
Issue descriptionIn issue 309362 , we observed that Steam was keeping some Chrome binaries locked in such a way as to block the rename dance. When this happens, it would be nice if we could provide some guidance. For example, we could open a tab to an HC article that described steps such as: - make sure no chrome.exe processes are running - log off and back on - temporarily disable any other software running in the background for any power users, we could even suggest that they run Process Explorer or Process Hacker to find out what program(s) have Chrome files locked.
,
Nov 20 2017
This still seems reasonable to do.
,
Nov 21
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by sheriffbot@chromium.org
, Sep 6 2017Status: Untriaged (was: Available)