DescriptionDon't accidentally propagate Omaha variable to child processes.
Short term fix to issue 174203 (when Chrome is launched by Omaha post-install, it fails when attempting to install the App Launcher).
Should be reverted when issue 174953 is fixed and widely deployed.
R=brettw
BUG=174203, 174953
TEST=SET GoogleUpdateIsMachine=1 and then launch chrome.exe. Using procexp, verify that the environment variable is not present in the running process.
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=181394
Patch Set 1 #Patch Set 2 : Move from chrome_constants to env_vars. #Patch Set 3 : Fix a silly mistake. #
Messages
Total messages: 6 (0 generated)
|