To keep Chrome within CRD from conflicting with Chrome running on the
local console, CRD currently sets CHROME_USER_DATA_DIR to a custom
location. However, this can cause issues if the user has multiple
channels installed, as they will all try to use this same profile
directory. This can lead to errors such as "Your profile can not be used
because it is from a newer version of Google Chrome" if, e.g., the user
tries to use Stable after using Beta.
M61 introduced a new CHROME_CONFIG_HOME environment variable, which
instead specifies a base directory in which Chrome will create channel-
specific data directories. This allows us to tell Chrome to store config
data in a separate location when running under CRD without interfering
with the ability to run multiple Chrome channels.
M61 is old enough by now that it makes sense to set CHROME_CONFIG_HOME
by default in CRD rather than CHROME_USER_DATA_DIR, which is exactly
what this change does. To prevent interfering with existing users who
already have a Chrome profile created under previous versions,
CHROME_USER_DATA_DIR is still set (and not CHROME_CONFIG_HOME) if the
old chrome-profile directory exists and the new chrome-config directory
does not.
Change-Id: I25feed41488d55998de9557fd63091426e4d09d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121435
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#753682}
054d9525b7