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

Issue 808925 link

Starred by 9 users
Status: Fixed
Owner:
k...@chromium.org
Closed: Feb 2018
Cc:
tommycli@chromium.org
█ skanuj@chromium.org
samans@chromium.org
jdonnelly@chromium.org
nyerramilli@chromium.org
mpear...@chromium.org
rbasuvula@chromium.org
pkasting@chromium.org
arthurso...@chromium.org
k...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Second entry in onmibox suggestion appears blank.

Reported by aiman.an...@etouch.net, Feb 5 2018 
Chrome Version:	66.0.3339.0 (Official Build) Revision eede49c2a7bfdd0a69d5254981bf629765ca57f7-refs/heads/master@{#534290} (32/64-bit)
 	
OS: Win(7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.13.3) and Linux(14.04 LTS).

What steps will reproduce the problem?
1. Launch chrome, in omnibox enter 'chrome://se' and observe second entry in suggestion list.

Actual: Second result in suggestion search list appears blank.

Expected: Suggestion search list should be displayed properly.

This is a regression issue, broken in M-66 series, and will soon update bisect info.

Manual Bisect:
Good Build:66.0.3338.0
Bad Build:66.0.3339.0
Actual Result.mp4
1.1 MB View Download
Expected Result.mp4
670 KB View Download

Comment 1 by aiman.an...@etouch.net, Feb 5 2018

Labels: hasbisect-per-revision RegressedIn-66 FoundIn-66 Target-66
Owner: k...@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,

Good Build:66.0.3338.0(Revision:534243)
Bad Build:66.0.3339.0(Revision:534290)

You are probably looking for a change made after 534252 (known good), but no later than 534253 (first known bad).

CHANGE-LOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/317c7b55e9783201af3fca42c308327294074518..0b180e48e0c416729c0913bc41574a1c9b874306

Suspect: https://chromium.googlesource.com/chromium/src/+/0b180e48e0c416729c0913bc41574a1c9b874306

krb@:Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thank You!

Comment 2 by aiman.an...@etouch.net, Feb 5 2018

Labels: ET-MUM-Reported

Comment 3 by rbasuvula@chromium.org, Feb 5 2018

Labels: ReleaseBlock-Stable
Adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!

Comment 4 by k...@chromium.org, Feb 5 2018

Cc: k...@chromium.org
 Issue 809082  has been merged into this issue.

Comment 5 by mpear...@chromium.org, Feb 7 2018 

We're getting multiple reports of this every day.  Do you have an update / fix?  If one is not coming soon, I recommend reverting the problematic change; this is clearly impacting people's workflows.

Comment 7 by k...@chromium.org, Feb 7 2018 

Issue 809941 has been merged into this issue.

Comment 8 by k...@chromium.org, Feb 7 2018

Cc: arthurso...@chromium.org skanuj@chromium.org
 Issue 809974  has been merged into this issue.

Comment 9 by k...@chromium.org, Feb 7 2018

Cc: samans@chromium.org tommycli@chromium.org jdonnelly@chromium.org pkasting@chromium.org mpear...@chromium.org
 Issue 810001  has been merged into this issue.

Comment 10 by k...@chromium.org, Feb 7 2018 

 Issue 810151  has been merged into this issue.

Comment 11 by jamescook@chromium.org, Feb 7 2018

Labels: OS-Chrome
Can you revert the problematic change? The DCHECKs this causes are impacting my work.

(For other who find this bug: Commenting out the DCHECK in autocomplete_result.cc is not sufficient to work around this.)

Comment 12 by k...@chromium.org, Feb 12 2018

Status: Fixed (was: Assigned)
This has been reverted; no new reports since.

Comment 13 by jdonnelly@chromium.org, Feb 13 2018 

The revert is here: https://crrev.com/c/906973.
►

Sign in to add a comment