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

Issue 736210 link

Starred by 6 users
Status: Duplicate
Owner:
thomasanderson@chromium.org
Closed: Jun 2017
Cc:
gov...@chromium.org
nyerramilli@chromium.org
ligim...@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
bashi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regreesion : #61.0.3139.0 build does not launch on second fresh installation.

Reported by avsha...@etouch.net, Jun 23 2017 
Chrome Version : 61.0.3139.0 (Official Build) 2dd0ea84298d45e0962c595c591529bc84dd0ebd-refs/heads/master@{#481757} 32/64 bit
OS : Windows(7,8,10)

What steps will reproduce the problem?
1. Freshly install chrome and launch it.
2. Now uninstall chrome from control panel.
3. Try to install the same build #61.0.3139.0 again.
 
Actual Result : #61.0.3139.0 build does not launch on second fresh installation.

Expected Result : #61.0.3139.0 build should install and launch properly.

This is a regression issue broken in ‘M-61’, below is the Manual Regression range and will soon update other info.
Good build : 61.0.3138.0
Bad build : 61.0.3139.0

Note : Will soon update other OS info.

Comment 1 by avsha...@etouch.net, Jun 23 2017

Labels: OS-Linux OS-Mac
Update : 

While uninstalling canary #61.0.3139.0 build on Windows OS, uninstall confirmation bubble was not displayed but chrome got removed from the machine. On second installation, build gets installed but does not launch (Windows task manager shows 2 "Google Chrome" processes running in background).

Note : Issue is also seen in Mac(10.11.6, 10.12.3) OS and Linux build is also failed. #61.0.3139.0 build is crashing in Mac OS on first launch.

Will soon update bisect info.

Comment 2 by mart...@martijnc.be, Jun 23 2017 

Same problem on OSX. This seems related to something in the profile, Chrome Canary starts once after deleting the profile directory (~/Library/Application Support/Google/Chrome Canary).

I don't have access to chrome://crashes because the crashes are stored in the profile that won't start. My client ID as requested on https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug:

client_id: 5379262850713605995
client_id2: 4606876e-5ba0-4508-8615-bed550d8716b

I can upload the crash dumps from the faulty profile in case the crash reports didn't upload.

Comment 3 by ranjitkan@chromium.org, Jun 23 2017

Cc: gov...@chromium.org ligim...@chromium.org
Labels: ReleaseBlock-Dev
Owner: thomasanderson@chromium.org
Status: Assigned (was: Unconfirmed)
From the change log suspecting below change could be a possible culprit which may have resulted in this failure:

Change Log: https://chromium.googlesource.com/chromium/src/+log/61.0.3138.0..61.0.3139.0?pretty=fuller&n=10000

https://chromium.googlesource.com/chromium/src/+/4312d5e0b01af9a3ad5f92a1763142155f01a7c6

@thomasanderson: Assigning to you, kindly take a look into it. 

Thanks.!

Comment 4 by rbasuvula@chromium.org, Jun 23 2017

Labels: -OS-Linux

Comment 5 by ranjitkan@chromium.org, Jun 23 2017

Cc: bashi@chromium.org
@ bashi: Also looping you, could you also please take a look into it as on MAC launching chrome, it just simply crashes, which I guess is addressed in issue 736251.

Change URL: https://chromium.googlesource.com/chromium/src/+/85241f184bc209cc43e1552b2113806e9f3321a7

Thanks.!

Comment 6 by mark@chromium.org, Jun 23 2017

Mergedinto: 736251
Status: Duplicate (was: Assigned)
►

Sign in to add a comment