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

Issue 671298 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

When searching from Omnibox in a new tab, I get no results. When I try a second time (or use an older tab) it works

Reported by adamlieb...@gmail.com, Dec 5 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
1. Open new tab in chrome
2. Enter search terms in omnibox
3. hit enter

What is the expected behavior?
To see a page of google search results

What went wrong?
Nothing happens. It shows a search URL for a couple seconds, but then resorts to about:blank. If I then search a second time, it works fine

Did this work before? Yes Not sure, but this used to not be a problem for me.

Chrome version: 54.0.2840.99  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

This is only a problem when searching for the first time in a new tab. If I search using omnibox on an already-open time, it works fine the first time.
 

Comment 1 by ajha@chromium.org, Dec 6 2016

Components: UI>Browser>Search
Labels: M-54
Does the problem reproduce on a clean profile?
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Win-10, Ubuntu 14.04 and Mac 10.12.1 using chrome reported version #54.0.2840.99, latest stable #55.0.2883.75 and latest canary #57.0.2939.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Uninstalled chrome and installed again.
2. Opened new tab in chrome.
3. Entered search terms in the omnibox.
4. Hit enter.
5. Observed that the page loaded with google search results.

adamliebowitz@ - Could you please check this issue on latest stable #55.0.2883.75 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.
671298.mp4
604 KB View Download
What does it mean to create a new profile? Create a new google account and log in to chrome with that? Or just log out of Chrome and try it without any account signed in?
See the "Add a person" section of https://support.google.com/chrome/answer/2364824 .
Very interesting! I followed the advice above and chose "browse as a guest" since I didn't have another persona to log in as. And, the problem mostly went away.

I say mostly because I could open a new tab, enter search terms in Omnibox, and after hitting enter would eventually be brought to a screen with the search results. It did seem to take a long time though.

To offer more details: when I perform a search logged in as myself, it briefly shows a long URL in the address bar with my search terms, and then immediately reverts to "about:blank". When I perform the search while browsing as a guest, it displays that long URL with the search term for an extended time (maybe 4-5 seconds) and then quickly proceeds to the search results page.

Does this info help to solve the original problem?
Note that creating a new Chrome account is entirely unrelated to having a gmail account, at least on Windows where you filed this bug.  You don't need to sign in the new Chrome account to sync at all (indeed, it's better not to).

I suspect the "long URL" is expected (omnibox search URLs are long).

I would go back to your original profile and try disabling the extensions in your extensions page, and see whether that helps.  If so, you can narrow down to if there's a specific extension causing this.
Ok. Going to try this now. First need to find where the 'extension page' is, but I'll search for it. 

I don't understand what you mean though by "You don't need to sign in the new Chrome account to sync at all (indeed, it's better not to)."
Actually, the problem suddenly no longer exists.  I don't understand why or how. But now my original profile is behaving just like the "guest" profile did. It takes longer than expected, but does eventually load the page the first time. Did browsing as guest and then switching back to original somehow eliminate the glitch? Seems that's the case.

Also, for the record, the initial bug I describe on this thread did not only happen with search terms. It also happened if I opened a new tab and clicked one of my bookmarks. When opening a new tab any action I first tried to do would resort in a about:blank page, and then would work on 2nd try.
Navigate to chrome://extensions, or use the app menu > More Tools > Extensions.

You spoke about "another persona to log in as".  "logging in" is only a relevant concept on ChromeOS, or if you're trying to connect a Chrome profile to a Google account for sync purposes.  If you simply create a new profile on desktop, you don't need to associate it with any account (i.e. you don't need to enable sync), and there's no such thing as "logging in".  So you can create as many such test profiles as you want.
@9: I would still check whether changing certain extensions helps.  It also sounds like you may be using a proxy, which is introducing problems or delays.  This can be controlled by an extension, or you may want to modify your proxy settings, which can be gotten at from the advanced section of Chrome's settings menu.
Project Member

Comment 12 by sheriffbot@chromium.org, Dec 15 2016

Labels: -Needs-Feedback Needs-Review
Owner: krajshree@chromium.org
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-Feedback
No, this is still Needs-Feedback.
Are you waiting for a comment from me? I'm not sure what happened, but the problem seems to be fixed. Must have been a big with my computer or internet connection that lasted a number of weeks but then went away. Sorry I couldn't be more helpful in diagnosing it
Status: WontFix (was: Unconfirmed)
I guess the bug can be closed, I just wanted to make sure the problem hadn't returned, and was curious if you'd checked the extension/proxy settings mentioned in comment 11.
Oops, I never responded to this. Yes I had checked the extension/proxy
settings but everything was already as recommended

Sign in to add a comment