New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 663703 link

Starred by 4 users

Issue metadata

Status: Verified
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 0
Type: Bug-Regression



Sign in to add a comment

Regression: 56.0.2914.0 unable to Un-install.

Project Member Reported by ajha@chromium.org, Nov 9 2016

Issue description

Version: 56.0.2914.0
OS: Windows-10

What steps will reproduce the problem?
(1) Launch chrome and install signed/unsigned PGO build of 56.0.2914.0
(2) Try to uninstall and check.


What is the expected result?
> Should uninstall.
What happens instead?
> Unable to uninstall.

Please use labels and text to provide additional information.

 

Comment 1 by ajha@chromium.org, Nov 9 2016

Labels: OS-Windows

Comment 2 by grt@chromium.org, Nov 9 2016

taking a look now
Cc: kavvaru@chromium.org
Able to reproduce the issue on windows 7 as well using chrome version 56.0.2914.0

Comment 4 by ajha@chromium.org, Nov 9 2016

Cc: grt@chromium.org
Labels: hasbisect
Regressed b/w previous canary(56.0.2913.0) and the latest(56.0.2914.0).

Last good build: 56.0.2913.0
First bad build: 56.0.2914.0

Changelog:
https://chromium.googlesource.com/chromium/src/+log/56.0.2913.0..56.0.2914.0?pretty=fuller&n=10000
Cc: pbomm...@chromium.org msrchandra@chromium.org ranjitkan@chromium.org

Comment 6 by grt@chromium.org, Nov 9 2016

Unable to repro. I just tried the unsigned win, win64, and win64-pgo with:

mini_installer.exe --chrome-sxs --verbose-logging

all three worked for me.

Could you provide more info on how you are running the installer and the exact nature of the failure? Could you attach %TEMP%\chrome_installer.log?
Summary: Regression: 56.0.2914.0 unable to Un-install. (was: Regression: 56.0.2914.0 unable to install.)

Comment 8 by ajha@chromium.org, Nov 9 2016

Cc: gov...@chromium.org

Comment 9 by grt@chromium.org, Nov 9 2016

Cc: -grt@chromium.org
Owner: grt@chromium.org
Status: Started (was: Untriaged)
This is caused by my commit at r430728. I'll revert it and merge the revert to the branch.

Comment 10 by grt@chromium.org, Nov 9 2016

Reverted on trunk at r430914.

Comment 11 by ajha@chromium.org, Nov 9 2016

Labels: Stability-Crash
Thanks for the quick turnaround and revert.

Just to update, seeing one installer related top crash on Windows canary(56.0.2914.0) with magic signature:install_static::`anonymous namespace'::AppendChromeInstallSubDirectory as well and probably rooted to r430728.

Link to the crashes:
====================
https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.ptype%3D%27Chrome%20Installer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27install_static%3A%3A%60anonymous%20namespace%5C%27%3A%3AAppendChromeInstallSubDirectory%27%20AND%20product.name%3D%27Chrome%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D

Comment 12 by grt@chromium.org, Nov 9 2016

Revert merged to 2914 at https://crrev.com/42f2553. Can anyone on the thread re-spin the Windows builds?

Comment 13 by grt@chromium.org, Nov 9 2016

Yes, that crash is the one.
re-triggered Win builds on 2914 branch, will monitor and update the bug with details

Comment 15 by grt@chromium.org, Nov 9 2016

Status: Fixed (was: Started)
Marking as fixed since the offending change has been reverted on trunk and branch.

Comment 16 by grt@chromium.org, Nov 9 2016

It turns out that r430728 resulted in a test failure on the win_trunk continuous builder. I didn't get a nag email about the failure. If I had, I would have reverted this sooner. I'm enquiring with infra to find out why I didn't hear about the test failure.
Status: Verified (was: Fixed)
grt@, thank you for the revert. Latest trunk#56.0.2914.1 is working fine w/o any issues.

Thank you Amit (ajha@) for finding this blocker issue.

Sign in to add a comment