Issue metadata
Sign in to add a comment
|
Regression : Chrome crashes while closing a sign in overlay.
Reported by
yfulgaon...@etouch.net,
Jan 17 2017
|
||||||||||||||||||||||
Issue descriptionChrome Version : 57.0.2984.0 (Official Build) a2377c097a1fa051f90f9c02d96d010073fcb701-refs/heads/master@{#443964} 64 bit OS : Mac(10.12.1, 10.11.6, 10.12) What steps will reproduce the problem? 1. Launch chrome, open two new chrome windows side by side and navigate to chrome://settings page in both the windows. (Please review an attachment) 2. In a first window, on settings page click on ‘Sign in to Chrome’ button (Sign in overlay appears). 3. Go to second window and click on ‘Sign in to Chrome’ button. 4. Now in a first window, in sign in overlay, click on “X” icon 2-3 times, observe. Actual : Chrome crashes while closing a sign in overlay in a first window. Expected : Chrome should not crash. Crash ID f68d352a-de7c-4fa0-a070-95aa58f65fb8 (Server ID: 31d0837a80000000) This is a regression issue broken in ‘M-51’, below is the Manual Regression range and Narrow Bisect info. Good build : 51.0.2699.0 Bad build : 51.0.2701.0 Narrow Bisect info : https://chromium.googlesource.com/chromium/src/+log/66c031ca891e491a2b6e96dcad92d9df2d4f7d43..7937328bb9f2e20cc2d4115a99919f6222d6d3f2?pretty=fuller&n=10000 Suspecting : r385225 from Narrow Bisect @anthonyvd : Please take a look. Note : This is Mac specific issue and the same is not reproducible on Windows & Linux OS.
,
Apr 18 2017
+msarda since I don't work on Identity anymore.
,
Apr 20 2017
Jerome: Could you test and see if you can still reproduce this bug?
,
May 22 2017
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 29 2017
Yes, I can reproduce this bug.
,
May 30 2017
with 61.0.3114.0 Sending to msarda since he worked on a similar crash.
,
May 29 2018
--Chrome Identity automated triaging-- This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 28 2018
--Chrome Identity automated triaging-- This available, signin or profiles-related bug has gone at least 30 days since the last automated post without any further update. This bug will be closed out due to inactivity. Please re-open the bug and provide an update if it is still a valid or reproducible bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Feb 16 2017