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

Issue 657805 link

Starred by 1 user
Status: WontFix
Owner:
█ tsergeant@chromium.org
Not on Chrome
Closed: Oct 2016
Cc:
nyerramilli@chromium.org
█ tkonch...@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Browser crash is seen after sign in from 'Tabs from other devices' at chrome://history.

Reported by jshan...@etouch.net, Oct 20 2016 
Chrome Version: 56.0.2896.0 (Official Build) eb410d934c054b358be84d4bc63724e99cefa7c8-refs/heads/master@{#426358}-32/64 bit
OS: Windows (7,8,10)

Pre-condition: 
1. Ensure that there are 2-3 history entries created by navigating any web pages.
2. Ensure that 10-15 entries exist in Tabs from other devices  

Steps:
1. Launch Chrome and navigate to chrome://history.
2. Click on iron icon of any entry and select 'More from this site'.
3. Now click on 'Tabs from other devices' and click on 'Sign in' button
4. Sign in with valid credential and observe.

Actual: Browser crash is seen after sign in from 'Tabs from other devices'.

Expected: Browser should not crash.

This is a regression issue broken in M-56, below is bisect info.

Good build: 56.0.2895.0
Bad build: 56.0.2896.0

Changelog URL: Providing changelog url as unable to sign in to Chromium builds.
https://chromium.googlesource.com/chromium/src/+log/56.0.2895.0..56.0.2896.0?pretty=fuller&n=10000

Suspecting: r426181 ?

@tsergeant, Could u please take a look and help to re-assign if your change is not the cause for this issue.

Crash id: 52d675a0-6c49-4273-9802-55de9c694531 (Server ID: 7383612b00000000)

Note: Above issue is not seen on Mac and Linux OS
Actual_video.mp4
1.8 MB View Download

Comment 1 by tsergeant@chromium.org, Oct 20 2016 

The CL you suggest as culprit only changes some CSS and should not be able to crash the browser.

The crash report does not show anything immediately useful -- the crash while processing a network request.

jshanbal: A few questions,

1) Are you certain this is the correct crash report? The crash server is showing the one you link as from 56.0.2894.0, which a good build, according to the original bug report.

2) Are the preconditions necessary? Does the crash occur with any search in the search box? Or no search in the search box?

Comment 2 by jshan...@etouch.net, Oct 21 2016 

With response to comment #1, unable to reproduce the issue on latest canary version 56.0.2897.0

Comment 3 by tsergeant@chromium.org, Oct 21 2016

Status: WontFix (was: Assigned)
Alright, marking as WontFix. Please re-open if you have a reliable repro.
►

Sign in to add a comment