Issue metadata
Sign in to add a comment
|
asan opt-out not working
Reported by
w...@phase.net,
Feb 11 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3009.1 Safari/537.36
Steps to reproduce the problem:
1. Set cohort hint: asan-optout in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Update\ClientState\{430FD4D0-B729-4F61-AA34-91526481799D}\cohort
2. Wait for update
3.
What is the expected behavior?
do not get an asan build
What went wrong?
I got an asan build
Did this work before? Yes, I've previously been opted out.
Chrome version: 58.0.3009.1 Channel: canary
OS Version: 10.0
Flash Version:
see screenshot
,
Feb 12 2017
{430FD4D0-B729-4F61-AA34-91526481799D} is the ID of the updater, not of Chrome Canary - you need to use {4EA16AC7-FD5A-47C3-875B-DBF4A2008C20}. Additionally, you need to use the HKEY_CURRENT_USER hive, instead of HKEY_LOCAL_MACHINE; you should already have a {4EA16AC7-FD5A-47C3-875B-DBF4A2008C20} key in the appropriate place - set cohorthint = asan-optout there.
As for why it appeared to be working in the past, we only release ASAN to a percentage of the population, it's likely that you were never "opted out" but instead just repeatedly landed in the percentage that got the non-ASAN build.
Were there instructions or documentation you were following to opt out? If so, I would like to correct them.
,
Feb 13 2017
yes you're right I was looking at the wrong product - when I check HKEY_CURRENT_USER\SOFTWARE\Google\Update\ClientState\{4EA16AC7-FD5A-47C3-875B-DBF4A2008C20}\cohort I have no hint set (I was sure I had set it before...)
I'll set the hint again and see if that works.
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by wfh@chromium.org
, Feb 11 2017