Regression: Browser gets crashed after sign into chrome at second instance.
Reported by
rk...@etouch.net,
Apr 22 2016
|
||||||
Issue descriptionChrome Version: 52.0.2715.0 Revision 3fae42f136f929251b627b2ae6300100afc8ab83-refs/heads/master@{#388964}(32/64 bit) OS: Windows (Win 7-Aero enabled),Linux,Mac Pr-Condition: Sign into chrome with valid credentials. What steps will reproduce the problem? (1) Launch chrome, navigate to chrome://md-settings and click on 'SIGN OUT' button. (2) Again sign into chrome with valid credentials and observe Browser gets crashed after sign into chrome at second instance. Crash ID 2fe51b9200000000 (08b5cba5-0284-4491-8eb8-37f48cbf3516) Browser should not crash. This is a regression issue,broken in 'M-52' ,below is bisect info: Good Build: 52.0.2712.0 Bad Build: 52.0.2713.0 ChangeLog URL: https://chromium.googlesource.com/chromium/src/+log/52.0.2712.0..52.0.2713.0?pretty=fuller&n=10000 Suspecting: r388129 Note: 1. Unable to Sign in to chrome in Chromium builds, hence providing suspect from Changelog URL. 2. Unable to capture video for the above issue.
,
Apr 22 2016
chrome://md-settings is under active development and is not released yet, as it is not production ready. I don't see why this should be blocking the Stable release so removing. Re-assigning to @tommycli, since this seems related to people-page.
,
Apr 22 2016
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12 2016
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 3 2016
Just to update: Above issue is not reproducible on latest canary 55.0.2878.0, hence marking as wontfix. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by nyerramilli@chromium.org
, Apr 22 2016