New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 602023
Owner: ----
Closed: Jan 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression

Sign in to add a comment

Issue 681068: Automatic Update downgrades 64 bit to 32 bit

Reported by, Jan 13 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2980.0 Safari/537.36

Steps to reproduce the problem:
1. Running Canary 64 bit
2. click to relaunch Canary as indicated for an update
3. After re-launch - Canary is now running 32 bit version

What is the expected behavior?
It should be running the 64 bit version

What went wrong?
It applied the update for the 32 bit version instead of the 64 bit version - downgraded Canary from 64 to 32 bit while updating it.

Did this work before? Yes Yesterday

Chrome version: 57.0.2980.1  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0

I have had this happen a couple of times. Th requires that Canary be removed (uninstalled via control panel) and then a fresh full installation. Whenever this has happened the 32 bit version seems to b at a on dot higher level that the 64 bit version.I just updated on two (2) windows instances with about 10 minutes of each other. The first update (on my home desktop) worked as expected  64 bit install and it updated to Version 57.0.2980.0 (Official Build) canary (64-bit). Several minutes later I clicked the "relaunch" on my corporat laptop (also running 64 bit) however after the rstart I it is now running 32 bit - Version 57.0.2980.1 (Official Build) canary SyzyASan (32-bit) - a ".1" level higher than the 64 bit version on the first instance updated.

Comment 1 by, Jan 13 2017

Sorry for the typos - I am having issues with a flakey keyboard,

Comment 2 by, Jan 16 2017

Labels: Needs-Triage-M57

Comment 3 by, Jan 19 2017

Mergedinto: 602023
Status: Duplicate (was: Unconfirmed)
This is the expected behavior. See for an explanation of what is happening, and for instructions on how you can opt-out of receiving ASAN builds. Note that uninstalling and reinstalling canary Chrome will remove the opt-out, so you must run the "reg add" command *after* you reinstall. Alternatively, run the "reg add" command and just wait patiently for the next update. Thanks for helping make Chrome awesome!

Comment 4 by, Jan 19 2017

Thanks for the information.

I am not sure what is meant by "To limit user pain we filter for machines with sufficient memory, as there is a significant memory overhead to the instrumentation.". Is this really working for selection ? In this case I updated both home & corporate asset within minutes of each other. Home desktop has 24GB memory and can easily handle what you describe. Corporate asset only has 8GB memory and is usually running memory starved (or close to being in a swap condition). I gave seen this in this several times - probably because when the swap happens on the corporate laptop Canary has trouble re-starting (I have a couple of the IBM support pages always open and they are launched on start-up  - real pigs for memory). My home system cam easily handle this - not the corporate asset. I just probably have not noticed the swap on this one when it happens. I have set the opt-out on the corporate asset.

Please clarify - will it automatically switch back to the 64 bit version on a later update if th registry hint is not set or is it necessary to manually uninstall & run full new install of the 64 bit version ?

Comment 5 by, Jan 23 2017

Without the hint in the registry, your machine will have a 1 in 20 chance on each update (~daily) of getting an ASAN build. If you take no action, you will most likely switch back to non-ASAN the day after you get it. You can use chrome://help to check for an update.

Sign in to add a comment