Issue 178705 in chromium: Address bar (Omnibox) typing is awfully slow

3,642 views
Skip to first unread message

chro...@googlecode.com

unread,
Feb 27, 2013, 7:43:14 AM2/27/13
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Area-UI Pri-2 Via-Wizard Type-Bug OS-Windows

New issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox) typing is
awfully slow
http://code.google.com/p/chromium/issues/detail?id=178705

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

Steps to reproduce the problem:
1. Open the browser
2. Start typing a search term in the Omnibox.
3. It's very slow. My computer isn't so slow, it used to be faster, but the
more time goes by the slower it gets, it's probably the history (which I
don't want to delete).

What is the expected behavior?
It should be fast.

What went wrong?
Omnibox becomes unresponsive and it takes about 300ms and even more for
each letter from the moment it's pressed until the browser executes the
action.

Did this work before? Yes When I first installed the browser.

Chrome version: 26.0.1403.0 Channel: stable
OS Version: 6.2 (Windows 8 Pro)

Suggestions:
If a backing thread is slowing it up, a special search algorithm should be
written, so in addition to the thread being asynchronous, it should be
pre-filtered so if the number of entries is too high, some entries should
automatically be pre-deleted or pre-ignored.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Feb 27, 2013, 7:45:14 AM2/27/13
to chromi...@chromium.org

Comment #1 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
This issue has been reported before, but was closed:
https://code.google.com/p/chromium/issues/detail?id=83460

chro...@googlecode.com

unread,
Feb 27, 2013, 7:52:14 AM2/27/13
to chromi...@chromium.org

Comment #2 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
This answer solved the issue:
http://goo.gl/2kndH

This should be avoided. I don't think the user has to mess with the
internal files once in couple of months. Hence this issue should remain
open until it's solved.

chro...@googlecode.com

unread,
Mar 19, 2013, 6:18:16 PM3/19/13
to chromi...@chromium.org
Updates:
Labels: -Cr-UI Cr-UI-Browser-Omnibox

Comment #5 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Hi Weitzhandler,

Sorry it looks like no one noticed this bug report.

This sounds awful.

Are you willing to help us debug it? If so, can you please go to
chrome://omnibox and type in something you normally type in the omnibox?
Check these three boxes too:
Show incomplete results
Show all details
Show results per provider, not just merged results

Then upload the output to this bug.

(For your information, the first and third checkboxes will together let us
see which parts of the omnibox system are slow and how slow they are. The
second box on that list will help us diagnose possible particular causes of
slowness.)

Here's one way to save the output of the page:
1. On the Chrome menu, open Tools -> Developer Console. Something should
appear on the bottom half of your window.
2. Click on the leftmost tab, named "Elements". It may already be selected
by default for you.
3. In the text window below, there should be a line <html>. Put your mouse
over it and right-click.
4. Select "copy as HTML" from the menu that appears.
5. Open a text editor such as notepad, paste the text in there, save it,
and upload that file to this bug.

thanks,
mark

P.S. Do you have Instant enabled?

chro...@googlecode.com

unread,
Mar 19, 2013, 6:22:16 PM3/19/13
to chromi...@chromium.org
Updates:
Labels: Needs-Feedback

Comment #6 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
(No comment was entered for this change.)

chro...@googlecode.com

unread,
Mar 21, 2013, 12:13:18 PM3/21/13
to chromi...@chromium.org

Comment #8 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
OK.
The result is attached hereby.

Attachments:
Debug results.html 70.4 KB

chro...@googlecode.com

unread,
Mar 21, 2013, 12:33:08 PM3/21/13
to chromi...@chromium.org

Comment #10 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Can you also post your whole about:version information?

thanks,
mark

chro...@googlecode.com

unread,
Mar 21, 2013, 1:44:09 PM3/21/13
to chromi...@chromium.org

Comment #11 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
Sure thing.

Attachments:
About Version.htm 5.9 KB

chro...@googlecode.com

unread,
Mar 21, 2013, 2:06:09 PM3/21/13
to chromi...@chromium.org
Updates:
Status: Available

Comment #12 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
I'm bringing in a coworker for advice.

pkasting@, it looks like omnibox's synchronous pass is taking ~200ms.
Ugh. The user isn't in any unusual field trials. How do you usually debug
synchronous pass slowness?

chro...@googlecode.com

unread,
Mar 21, 2013, 3:23:11 PM3/21/13
to chromi...@chromium.org

Comment #13 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
@mpearson, and this isn't slow enough. Within a week or two it will go up
to 500ms and up.
So convince me that it's my task to delete the User Data file manually once
in a week.

chro...@googlecode.com

unread,
Mar 30, 2013, 12:15:25 AM3/30/13
to chromi...@chromium.org

Comment #14 on issue 178705 by pkas...@chromium.org: Address bar (Omnibox)
These results are strange. We don't get a call until 247 ms, but at that
point we not only have Search and HQP results but HCP results? And nothing
from the HUP?

Reporter, I assume this happens when you start to type a new query, right?
If so, can you give us the about:omnibox data for just one or two letters,
ideally ones which will autocomplete to a URL, instead of a long string?
(Mark: The goal here is to get the HUP to give us some results so we can
see how fast that comes back.)

We don't have a lot of infrastructure in place to time the different
providers. The Omnibox.QueryTime histograms provide overall timings for
everything combined, but they don't tell us which provider(s) are acting up.

chro...@googlecode.com

unread,
Apr 16, 2013, 6:24:59 PM4/16/13
to chromi...@chromium.org

Comment #17 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
@mpearson, I didn't understand, those parameters didn't seem to do the job,
are they build parameters?? or it's C:\Chrome\Chrome --force-etc.?

Anyway as the browser search box is now really running AWFULLY slow, I'm
now attaching another test result from about:omnibox, and that's before
deleting the History Provider Cache files
(http://superuser.com/a/298616/9825).

Attachments:
Slow omnibox.htm 15.1 KB
Fast omnibox.htm 15.1 KB

chro...@googlecode.com

unread,
Apr 16, 2013, 6:46:59 PM4/16/13
to chromi...@chromium.org

Comment #19 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
In that case, that's what I did, it didn't affect the speed at all.

chro...@googlecode.com

unread,
Apr 16, 2013, 6:53:59 PM4/16/13
to chromi...@chromium.org

Comment #20 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Also, Weitzhandler, the files you saved from the about:omnibox page don't
show anything. You can't "save as" the about:omnibox page. You can copy
and paste the contents, or you can follow the steps in comment #5 on this
bug to save proper HTML files. Either would be great! However, I'm still
most interested in the force-fieldtrials question, of whether any of those
magical commands line fixes the problem for you.

chro...@googlecode.com

unread,
Apr 17, 2013, 11:20:07 AM4/17/13
to chromi...@chromium.org

Comment #22 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Hi,

I'm very surprised that none of those command lines affected the slowness.

When you tested the first command line on that list (
--force-fieldtrials=AutocompleteDynamicTrial_3/DisabledProviders_1791/
), did you notice that you never got any URL suggestions? I'm asking
because I want to make sure the command line worked right for you. If you
don't remember, go ahead and test the command line again using the same
technique as you did before and tell me if URL suggestions still show up
when you type in the omnibox.

thanks,
mark

chro...@googlecode.com

unread,
Apr 17, 2013, 11:39:07 AM4/17/13
to chromi...@chromium.org

Comment #23 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
Hi mark and thanks for your self-dedication!

Nope, I don't remember, I didn't notice, I tested it just for a second,
once I saw it's still slow, I moved on to next flag.

chro...@googlecode.com

unread,
Apr 17, 2013, 2:17:24 PM4/17/13
to chromi...@chromium.org

Comment #26 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Yeah, it looks like the command line didn't do what it's supposed to.
Hmmm... How are you launching chrome when you try it with the command
line? Modify a shortcut? Start from a terminal?

chro...@googlecode.com

unread,
Apr 23, 2013, 4:44:01 PM4/23/13
to chromi...@chromium.org

Comment #28 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
OK.
It's slow back again.
Here are some tests:

1.html - An Omnibox test checking all checkboxes (Prevent inline
autocomplete, In keyword mode, Show incomplete results, Show all details,
Show results per provider, not just merged results.
2.html test, leaving the first two checkboxes blank.


Attachments:
1.html 866 KB
2.html 82.9 KB

chro...@googlecode.com

unread,
Apr 23, 2013, 6:01:44 PM4/23/13
to chromi...@chromium.org

Comment #32 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
(No comment was entered for this change.)

Attachments:
1694.html 19.6 KB
1695.html 19.6 KB
1727.html 19.6 KB
1791.html 15.1 KB

chro...@googlecode.com

unread,
May 3, 2013, 7:29:37 AM5/3/13
to chromi...@chromium.org

Comment #42 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
Another user here with omnibox slowness, deleting the history file doesn't
help the issue. Very noticeable lag when typing in the omnibox, which
started only few days ago. Omnibox debuf HTML attached, tried with
just "facebook".

Attachments:
omnibox.txt 99 KB

chro...@googlecode.com

unread,
May 3, 2013, 7:35:39 AM5/3/13
to chromi...@chromium.org

Comment #43 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
Another user here with omnibox slowness, deleting the history file seems
for now have solved the issue. Very noticeable lag when typing in the

chro...@googlecode.com

unread,
May 3, 2013, 9:18:15 AM5/3/13
to chromi...@chromium.org

Comment #44 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
apweine:

The omnibox.txt file you attached doesn't show any output. :-(

The next time this occurs, I have a whole series of requests for you. I've
had little luck debugging thus far, that's why I need so much information.
* Can you save the about:omnibox output using the technique described in
comment #5?
* Can you please try the experiment described in comment #15 of starting
Chrome with different command line parameters and tell me how it goes? In
between each restart, type a few characters in the omnibox after Chrome
starts and wait a minute to let everything in the omnibox system warm up,
then try actively using then omnibox and tell me if any of those command
lines are different.
* Can you post your about:version information here, and also the full list
of extensions you have installed?

thanks,
mark

chro...@googlecode.com

unread,
May 3, 2013, 12:36:26 PM5/3/13
to chromi...@chromium.org

Comment #45 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
Hi,

Thanks for swift reply! The file I attached was generated by using the
technique in comment #5. However double checking the uploaded file it
appears that the main body was cutoff, here is the same file again,
uploaded to pastebin: http://pastebin.com/n5BpnArc

Currently I am running Chrome with following commandlines:
--disable-new-menu-style --ssl-version-max=tls1. I will test the ones in
comment #15 ones the problem occurs again.

About:version

Google Chrome 26.0.1410.64 (Official Build 193017) m
OS Windows
WebKit 537.31 (@147513)
JavaScript V8 3.16.14.11
Flash 11.7.700.179
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML,
like Gecko) Chrome/26.0.1410.64 Safari/537.31
Command
Line "C:\Users\XXXXX\AppData\Local\Google\Chrome\Application\chrome.exe"
--flag-switches-begin --disable-webgl --enable-nacl --ignore-gpu-blacklist
--touch-events=disabled --touch-optimized-ui=disabled --flag-switches-end
Executable Path
C:\Users\XXXXX\AppData\Local\Google\Chrome\Application\chrome.exe
Profile Path C:\Users\XXXXX\AppData\Local\Google\Chrome\User Data\Default
Variations 5f9f065f-15eb91be
b03ddc1f-75e383c2
f9b252d0-fd526c81
dca78d1b-1944245
6b981c71-4ad60575
ca6785ad-766fa2d
3709139-766fa2d
ff3fc1a6-766fa2d
d86b76a4-766fa2d
7f6da4bf-dbbd7415
75f7fb7e-766fa2d
ad0f4b69-83e4f49c
24dca50e-837c4893
ca65a9fe-91ac3782
82d91892-3d47f4f4
3028188e-f758d5dd
5a3c10b5-e1cc0f14
244ca1ac-4ad60575
246fb659-9d9eea77
f296190c-4c073154
4442aae2-a90023b1
75f0f0a0-a5822863
e2b18481-cdc3d902
e7e71889-4ad60575

I am currently the following extensions:
AdBlock
imgur Extension by Metronomik
Lazarus: Form Recovery
Screen Capture (by Google)
Search by Image (by Google)

chro...@googlecode.com

unread,
May 6, 2013, 4:22:20 AM5/6/13
to chromi...@chromium.org

Comment #46 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
I am noticing the lag again, especially when typing "facebook" in a new tab
which takes omnibar up to a second or two to start reacting to.

chro...@googlecode.com

unread,
May 6, 2013, 11:43:58 AM5/6/13
to chromi...@chromium.org

Comment #47 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Hi apweine,

Can you try experimenting with the different command line parameters I
suggested?

thanks,
mark

chro...@googlecode.com

unread,
May 13, 2013, 12:34:00 PM5/13/13
to chromi...@chromium.org

Comment #49 on issue 178705 by m...@chromium.org: Address bar (Omnibox)
Has anyone tried this with Views Textfields disabled in about:flags
(--disable-views-textfields)?

chro...@googlecode.com

unread,
May 13, 2013, 7:06:06 PM5/13/13
to chromi...@chromium.org

Comment #54 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
> @mark, after relaunching chrome it's fast again, should I send it to you
> when it's slow again?

No, just send it to me anytime. I can launch Chrome with it and wait a
while until Chrome hopefully becomes slow.

chro...@googlecode.com

unread,
May 13, 2013, 8:47:09 PM5/13/13
to chromi...@chromium.org

Comment #57 on issue 178705 by Weitzhan...@gmail.com: Address bar (Omnibox)
Mark, please check your email.

chro...@googlecode.com

unread,
May 14, 2013, 7:51:45 AM5/14/13
to chromi...@chromium.org

Comment #58 on issue 178705 by phd....@gmail.com: Address bar (Omnibox)
I have the same problem with a slow responding omnibox. The longer I leave
chrome opened, the slower it becomes over time.

I´m using Windows 8. On several other machines with Windows 7 I do not have
this issue.

chro...@googlecode.com

unread,
May 17, 2013, 5:18:44 AM5/17/13
to chromi...@chromium.org

Comment #63 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
mpearson,

A while back I recall having an issue with chrome being noticeable slow on
rendering new tabs I've opened in the background. It was like the tab froze
for 1-2 seconds and the image of the original tab was sometimes kept on
screen instead of the new tab I switched to. That, however, was solved
couple of months ago.. And I don't even recall now what it was that I did.

Regarding current issue, as far as I can tell it is mainly omnibox. Chrome
does feel generally faster but it is nothing I directly notice or can
measure, it is mainly omnibox that draws attention regarding performance.
Pages themselves function normally.

chro...@googlecode.com

unread,
May 17, 2013, 8:46:06 PM5/17/13
to chromi...@chromium.org

Comment #64 on issue 178705 by fang.eug...@gmail.com: Address bar (Omnibox)
I'd like to add that I'm experiencing something very similar, but the
problem gets resolved if I fully close Chrome (making sure that not a
single chrome.exe process is running). If I could help the debugging
process in any way, please let me know.

chro...@googlecode.com

unread,
May 22, 2013, 1:27:47 AM5/22/13
to chromi...@chromium.org

Comment #65 on issue 178705 by glun...@gmail.com: Address bar (Omnibox)
I've had issues with the Chrome Omnibar ever since I switched to Mac. The
Omnibar often freezes for several seconds when I type in it. In addition,
there is sometimes a (short) delay when switching tabs for Chrome to show
the page. I have a very large number of bookmarks and I rarely close
Chrome. Should I delete my bookmarks? Clear my history? Regularly restart
Chrome?

I noticed there have been issues like this for many years
(https://code.google.com/p/chromium/issues/detail?id=6646), so is there
some way to fix the problem?

chro...@googlecode.com

unread,
May 22, 2013, 12:05:41 PM5/22/13
to chromi...@chromium.org

Comment #66 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
I have some good news. Tomorrow's dev channel update has code to help me
diagnose this problem. Who of experiencing this bug is on the dev channel
or willing to switch to it to help me fix out this?

(Weitzhandler, I already know you're on dev from your original bug report;
no need to answer.)

glunker, I don't know what advice to give you. In my experience (from this
bug and others), it sounds like restarting Chrome usually fixes the problem
for people for a while, but then it comes back. Ditto with clearing
history. I still am not sure whether this is caused by a user's profile
(history, etc.) or whether it's something problematic about the machine
itself that Chrome is running on. I'd appreciate it if you didn't do
anything too dramatic (such as clearing history)--I'd like your help
tracking down this bug and if you do that, you might not be able to help.
Also, by the way, the bug you link to when you say "I noticed there have
been issues like this for many years" was fixed in 2009. These latest
problems (described by this bug thread and a few others) all seem to have
started in 2013 sometime.

chro...@googlecode.com

unread,
May 22, 2013, 12:51:49 PM5/22/13
to chromi...@chromium.org

Comment #69 on issue 178705 by phd....@gmail.com: Address bar (Omnibox)
With "portable" I meant a zip file that I unzip somewhere, so that I can
use this version in parallel to my normal version. But never mind. Will
switch to dev tomorrov ...

chro...@googlecode.com

unread,
May 22, 2013, 1:02:49 PM5/22/13
to chromi...@chromium.org

Comment #70 on issue 178705 by sh...@chromium.org: Address bar (Omnibox)
Switching from stable to dev channel and back can go awry if the profile
information changes format.

Canary would work, it uses a different profile so you can run it in
parallel. If the problem repros there, that might be interesting.

chro...@googlecode.com

unread,
May 23, 2013, 11:33:24 PM5/23/13
to chromi...@chromium.org

Comment #73 on issue 178705 by fang.eug...@gmail.com: Address bar (Omnibox)
Couldn't reproduce the problem with limited testing on Canary (I copied all
of the profile stuff). But I got the symptoms to occur on Dev. Here are my
histograms.

Attachments:
before.txt 506 KB
after.txt 1.6 MB

chro...@googlecode.com

unread,
May 28, 2013, 2:08:13 PM5/28/13
to chromi...@chromium.org

Comment #74 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
fang.eugene:

You appear to not be running the latest dev version (Chrome 29). Can you
update and try to reproduce the problem again and then send me the before
and after histograms?

If you've restarted your browser since you sent me those histograms, you
may have already been updated. The way to make sure you're current is go
to chrome://settings/ and click on "Help" on the last side. It should
cause an update check.

thanks,
mark

chro...@googlecode.com

unread,
May 28, 2013, 7:12:33 PM5/28/13
to chromi...@chromium.org

Comment #76 on issue 178705 by fang.eug...@gmail.com: Address bar (Omnibox)
Mark,

That's odd, I'm pretty sure I was running Chrome 29 when I saved those
histograms. Oh well, I'll redo it.

Just to clarify, is before.txt supposed to be before the lag happens? Or is
it after the lag starts occurring but before using the omnibar after
navigating to about:histograms? Thanks.


-Eugene

chro...@googlecode.com

unread,
May 29, 2013, 7:52:17 PM5/29/13
to chromi...@chromium.org

Comment #77 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
> Just to clarify, is before.txt supposed to be before the lag happens? Or
> is it after the lag
> starts occurring but before using the omnibar after navigating to
> about:histograms? Thanks.

After the lag starts happening,
navigate to about:histograms,
save it as before.txt,
open a new tab,
play around with the omnibox for a bit,
go back to about:histograms tab,
reload it,
save it as after.txt.

chro...@googlecode.com

unread,
Jun 5, 2013, 12:55:43 PM6/5/13
to chromi...@chromium.org

Comment #79 on issue 178705 by fang.eug...@gmail.com: Address bar (Omnibox)
Okay here they are. Before and after are what you requested. I also
included pre.txt which was taken right after restarting Chrome, which may
be useful.

Attachments:
pre.txt 381 KB
before.txt 1.6 MB
after.txt 1.6 MB

chro...@googlecode.com

unread,
Jun 6, 2013, 9:25:23 PM6/6/13
to chromi...@chromium.org

Comment #80 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Anyone who has this problem, please try deleting the "History Provider
Cache" file in your profile's / user's data directory. Then restart
Chrome. I believe that should make the problem go away, at least for a
long, long time. (Weitzhandler, I believe your strategy is right. Thanks
for the tip.)

Everyone, you plan to try this, please tell me the size of the file before
you deleted it, and the size it is later. (By the way, it may not reappear
on the first Chrome restart. After that restart, wait a couple minutes,
then restart again. Then it should reappear so you can answer my question.)

If this helps or doesn't help the lagginess, I want to know. Please post
here.

thanks,
mark

chro...@googlecode.com

unread,
Jun 7, 2013, 8:02:48 AM6/7/13
to chromi...@chromium.org

Comment #81 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
Before deleting History Provider Cache: 5.68mb. When I closed Chrome new
file was created before I had the chance to re-launch it with size of
6.64mb.

chro...@googlecode.com

unread,
Jun 7, 2013, 9:42:51 AM6/7/13
to chromi...@chromium.org

Comment #82 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Oh, good point The file is written on Chrome exit.

You should quit Chrome, look up the file size, delete the file, then start
Chrome.

If you want to help me verify my theory, continue with: wait a minute, quit
Chrome, look up the file size, then start Chrome again. Tell me both the
file sizes.

chro...@googlecode.com

unread,
Jun 7, 2013, 11:04:42 AM6/7/13
to chromi...@chromium.org

Comment #83 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
6.71mb before exit, 2.14mb after startup. Chrome felt somewhat faster to
start too. However the omnibox problem wasn't present this try as last try
with deletion seemed to have fixed it for now.

chro...@googlecode.com

unread,
Jun 7, 2013, 8:48:42 PM6/7/13
to chromi...@chromium.org

Comment #84 on issue 178705 by bugdro...@chromium.org: Address bar
(Omnibox) typing is awfully slow
http://code.google.com/p/chromium/issues/detail?id=178705#c84

------------------------------------------------------------------------
r204985 | mpea...@chromium.org | 2013-06-08T00:04:02.430042Z

Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/history/url_index_private_data.h?r1=204985&r2=204984&pathrev=204985
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/history/in_memory_url_index_unittest.cc?r1=204985&r2=204984&pathrev=204985
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/history/in_memory_url_index_cache.proto?r1=204985&r2=204984&pathrev=204985
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/history/url_index_private_data.cc?r1=204985&r2=204984&pathrev=204985

Omnibox: Rebuild HQP Cache if it's old

Make sure the HQP data file is rebuilt from the on-disk history database
at least once a week. If this doesn't happen, the HQP will grow without
bound. Every time a URL is visited, it has the opportunity to be added
to the index. The HQP never expires anything from its index; it currently
only gets rid of only entries by rebuilding the cache from history.
Hence, we need to force rebuilds regularly.

A side effect of this change, which bumps the HQP's cache version
number, will cause all clients to rebuild their HQP database on the
first restart after this update.

BUG=230605, 178705, 237703, 168933
TBR=sky

Review URL: https://chromiumcodereview.appspot.com/15645012
------------------------------------------------------------------------

chro...@googlecode.com

unread,
Jun 9, 2013, 4:00:21 AM6/9/13
to chromi...@chromium.org

Comment #85 on issue 178705 by fang.eug...@gmail.com: Address bar (Omnibox)
Before: 4.33 MB
After: 0.927 MB

chro...@googlecode.com

unread,
Jun 16, 2013, 10:56:27 PM6/16/13
to chromi...@chromium.org

Comment #86 on issue 178705 by seansydn...@gmail.com: Address bar (Omnibox)
I don't want to intrude too much but for the past two weeks I've been
suffering the same issue as you. Sluggish omnibox, sometimes when I first
start typing into the box it actually completely skips/misses the first
letter as well. The issue appears to be random, as despite the fact I've
had the issue for a while, there was a period of two days where the issue
seemingly disappeared. Anyway, I changed the settings around as some
suggested, disabling prediction services etc to no avail. I took note of
the suggestion to delete the History Provider Cache, that appears to have
helped for now.

Size before deleting: 978kb
Size after deleting: 620kb.

Cheers.

chro...@googlecode.com

unread,
Jun 17, 2013, 5:05:28 AM6/17/13
to chromi...@chromium.org

Comment #87 on issue 178705 by seansydn...@gmail.com: Address bar (Omnibox)
Sorry, update:

The issue has returned.

I am willing to debug for someone willing to read the results.

Win7 64bit
Chrome Version 27.0.1453.110 m

chro...@googlecode.com

unread,
Jun 18, 2013, 4:50:21 AM6/18/13
to chromi...@chromium.org

Comment #89 on issue 178705 by Jason.A....@gmail.com: Address bar (Omnibox)
I would like to chime in and say that I've had a very similar problem with
Chrome for about a year or more now. It even seems to crop up on brand new
installs of Chrome on new computers (so maybe it is in my profile). I'm
glad to see there is a current and active effort to fix this problem. If
there is anything I can do to help, please ask.

chro...@googlecode.com

unread,
Jun 18, 2013, 12:31:22 PM6/18/13
to chromi...@chromium.org

Comment #90 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Hi Jason.A.Wilkins,

What version of Chrome are you running and on what platform?

thanks,
mark

chro...@googlecode.com

unread,
Jun 18, 2013, 11:45:17 PM6/18/13
to chromi...@chromium.org

Comment #92 on issue 178705 by seansydn...@gmail.com: Address bar (Omnibox)
ok so the issue is a bit ... fickle so it's hard to measure it consistently
but I recorded a histogram, and then the moment the omnibox missed a
keystroke I reloaded the histogram and saved that too.

The files uploaded were made from Skydribe Web Tools, so if the formatting
is messed up at all, that's probably why. They're simply .docx files
though, so it should be okay. If you'd like, I can give you a direct public
share link to the files on Skydrive, just be aware that it seems Internet
Explorer needs to be used to view large word files properly and I'd imagine
that's Microsoft's doing.

Anywho, I hope that's helpful. In fact, I hope the issue I have is even
measurable. We'll see.

Thanks for your help.


----

Also on a side note and related to Jason's post: I too use Google chrome
sync and have this feeling that it's possible that my data on Google's
servers is possibly corrupted. If we don't find a solution to this, then
I'll consider wiping all my data at:
https://www.google.com/settings/chrome/sync and wiping all data locally and
just starting 100% anew. I'd like to point out I've installed Canary
(without any profiles copied over or synced) and so far it has been
behaving, but I have not used it enough to know for sure.

Attachments:
Histogram_First[1].docx 152 KB
Histogram_second[1].docx 161 KB

chro...@googlecode.com

unread,
Jun 21, 2013, 4:46:01 PM6/21/13
to chromi...@chromium.org

Comment #93 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Hi seansydneybrennan,

Those histograms help a little bit. They're consistent with the other
reports I've seen but don't give me any new amazing insight. Can you try
the various experiments in comment #15 and tell me if any of those command
lines improve the situation? Note: Chrome will probably speed up a little
when you restart it, so please restart once, use Chrome to get a sense of
the omnibox's normal speed (not after it's been running for hours/days),
then restart again with those various command lines and mentally compare.
Also, be sure to wait a minute after Chrome starts up (even if it looks
like all pages are there, there might be stuff happening in the background
for a little longer). I don't want the startup time to bias your test.

thanks,
mark

chro...@googlecode.com

unread,
Jul 3, 2013, 10:06:58 AM7/3/13
to chromi...@chromium.org

Comment #94 on issue 178705 by seansydn...@gmail.com: Address bar (Omnibox)
Sorry for being MIA.

I fixed my problem:

The scenario:

On my computer I've set up a custom task under Task Scheduler which
automatically launches two particular services on system startup and those
particular services, when started up, have their own startup configurations
separate from what I had done. One of those is to automatically launch the
default web browser (Chrome) and to load their respective local GUI web
consoles, for convenience.

When I was investigating this omnibox issue, the thing I noticed was that
once I restarted Chrome, the issue never came back until the computer
restarted. Anyway, after a lot of thinking I decided to jump into these
services' configuration files and stop them from loading their console page
unless I manually access it from the address bar. So, Chrome would only
launch when I click its shortcut and their console pages would only ever
load when I type the address in manually to access it.

Long story short: No problems since.


TL;DR:

I fixed my problem because I stopped two services that I use which load on
system startup from automatically launching Chrome and loading up their web
console page. The services themselves still launch on startup via Task
Scheduler, they just don't muck with anything else anymore and do their own
thing.

chro...@googlecode.com

unread,
Jul 8, 2013, 7:49:13 AM7/8/13
to chromi...@chromium.org

Comment #95 on issue 178705 by Jason.A....@gmail.com: Address bar (Omnibox)
This happens too often for me! Chrome might take up to 2-3 minutes before
it becomes responsive again after typing in the omnibox.

I offered to help but nobody really followed up on that.

I wish I could just turn it off! I find it stupid that the devs won't at
least give me that option as a workaround for a bug that makes occasionally
Chrome unusable.

chro...@googlecode.com

unread,
Jul 9, 2013, 12:05:46 AM7/9/13
to chromi...@chromium.org

Comment #97 on issue 178705 by Jason.A....@gmail.com: Address bar (Omnibox)
@mpearson

Size of 'History Provider Cache' after exiting chrome the first time: 3,738
Kibibytes

Size after deleting the file and starting/exiting chrome again: 13 bytes

chro...@googlecode.com

unread,
Jul 9, 2013, 12:06:47 AM7/9/13
to chromi...@chromium.org

Comment #98 on issue 178705 by Jason.A....@gmail.com: Address bar (Omnibox)
I'll add that after leaving the previous comment and exiting Chrome again
it grew to 821 Kibibytes

chro...@googlecode.com

unread,
Jul 9, 2013, 9:41:20 AM7/9/13
to chromi...@chromium.org

Comment #99 on issue 178705 by mpea...@chromium.org: Address bar (Omnibox)
Jason, is the omnibox more responsive for you now?

chro...@googlecode.com

unread,
Jul 9, 2013, 9:45:20 AM7/9/13
to chromi...@chromium.org

Comment #100 on issue 178705 by Jason.A....@gmail.com: Address bar
I'm going to very cautiously say that it seems to be behaving normally
now. If it gets to the point where Windows decides to take over drawing
the client area again then I'll be sure to report it.

chro...@googlecode.com

unread,
Jul 9, 2013, 9:46:20 AM7/9/13
to chromi...@chromium.org

Comment #101 on issue 178705 by Jason.A....@gmail.com: Address bar
(Omnibox) typing is awfully slow
http://code.google.com/p/chromium/issues/detail?id=178705

I'm going to very cautiously say that it seems to be behaving normally
now. If it gets to the point where Windows decides to take over drawing
the non-client area again then I'll be sure to report it.

chro...@googlecode.com

unread,
Jul 14, 2013, 3:31:16 PM7/14/13
to chromi...@chromium.org

Comment #103 on issue 178705 by Weitzhan...@gmail.com: Address bar
Turns out I was so wrong.
Gonna delete HPC file now.

Size before: 1622KB
Size after deletion and restart: 600KB
BTW, take a look at the attached picture, there are other big files in that
folder.

Attachments:
RyoC0ZG.png 19.6 KB

chro...@googlecode.com

unread,
Jul 16, 2013, 8:57:27 AM7/16/13
to chromi...@chromium.org

Comment #104 on issue 178705 by ryanwag...@gmail.com: Address bar (Omnibox)
This is happening to me as well on 28.0.1500.72 (Windows 8).

Size before: 572KB
Size after deletion and restart: 312KB

After a little while I still experienced the issues, and so I cleared my
history and deleted the file again. It was 1KB after a restart then. It
sucks I had to clear my history, but I'm hoping this will buy me some more
time between needing to restart Chrome.

Also, looks like this is a related issue:
https://code.google.com/p/chromium/issues/detail?id=237703

chro...@googlecode.com

unread,
Jul 19, 2013, 6:27:22 PM7/19/13
to chromi...@chromium.org

Comment #105 on issue 178705 by mpea...@chromium.org: Address bar
Weitz..., since you're still seeing this problem (even after the hack to
delete the History Provider Cache), can you send me your about:histograms
data? I need all the Omnibox.* entries. If the browser is always slow (as
you imply), then try this experiment: start it. Wait until everything has
finished loading. Wait another minute. Then some a few inputs into the
omnibox (no need to hit enter, just clear the omnibox or open a new tab and
start again). Then go to about:histograms and give me the output.

thanks,
mark

chro...@googlecode.com

unread,
Jul 19, 2013, 6:31:22 PM7/19/13
to chromi...@chromium.org

Comment #106 on issue 178705 by mpea...@chromium.org: Address bar
apweine, from your last comment, it sounds like the method of deleting the
History Provider Cache has fixed the problem for you. Is that true? If
not, please say something.

chro...@googlecode.com

unread,
Jul 19, 2013, 6:40:22 PM7/19/13
to chromi...@chromium.org

Comment #107 on issue 178705 by mpea...@chromium.org: Address bar
fang.eugene, did deleting the History Provider Cache fix the problem for
you or are you still experiencing slowness?

chro...@googlecode.com

unread,
Jul 19, 2013, 6:47:22 PM7/19/13
to chromi...@chromium.org

Comment #108 on issue 178705 by Jason.A....@gmail.com: Address bar
A couple of days ago I started getting hang ups again. I may write a
script to delete the History Provider Cache every time I start Chrome until
this is fixed.

chro...@googlecode.com

unread,
Jul 19, 2013, 7:01:22 PM7/19/13
to chromi...@chromium.org

Comment #109 on issue 178705 by mpea...@chromium.org: Address bar
Jason.A.Wilkins: all versions of Chrome 29 and up will automatically
refresh the cache as needed. Right now Chrome 29 is in the Beta channel,
so if you're on dev or beta and still experiencing lag, then this isn't the
cause. If you're on the stable channel, you'll just need to wait a month
or two for the next update.

chro...@googlecode.com

unread,
Jul 21, 2013, 9:32:50 PM7/21/13
to chromi...@chromium.org

Comment #111 on issue 178705 by fang.eug...@gmail.com: Address bar
Mark,

I haven't had issues since.

chro...@googlecode.com

unread,
Jul 23, 2013, 1:12:43 AM7/23/13
to chromi...@chromium.org

Comment #113 on issue 178705 by Weitzhan...@gmail.com: Address bar
Hi Chris and thanks for your effort reproducing the issue.
I agree with every word said.

I would like to add, I'm now realizing that after restarting Chrome issue
is gone for a short while as Chris said, I believe this is something that's
been fixed recently, since I don't remember it used to help in the older
versions not sure which version tho :(

Hope the error is found and fixed quickly, this issue is incredibly
annoying.
Best regards

chro...@googlecode.com

unread,
Jul 23, 2013, 1:20:24 AM7/23/13
to chromi...@chromium.org

Comment #114 on issue 178705 by Weitzhan...@gmail.com: Address bar
BTW, I'm also that type of user that has his browser open always with lots
of pinned tabs and suffer from memory leaks too as Chris mentioned.

I think it would be great to have all the inactive tabs' activity and
scripts suspended until focused again.
My settings are configured so that when browser launches, all recent tabs
are opened, I think it would be great if first the focused tab should be
loaded, then all the rest should load silently on the background when idle
etc.

chro...@googlecode.com

unread,
Jul 24, 2013, 4:13:05 AM7/24/13
to chromi...@chromium.org

Comment #115 on issue 178705 by clay...@littlepiggiesgreencleaning.com:
Address bar (Omnibox) typing is awfully slow
http://code.google.com/p/chromium/issues/detail?id=178705

I am also having this problem. I leave two windows with 3-5 tabs open at
any given time. I normallly put the computer to sleep or hybernate, and do
not restart the browser often. I'm trying a few suggestions listed here

chro...@googlecode.com

unread,
Jul 24, 2013, 6:04:07 AM7/24/13
to chromi...@chromium.org

Comment #116 on issue 178705 by demono...@googlemail.com: Address bar
I've been following this for a while hoping Mark could find a solution.
I've tried a lot of the things mentioned and they seem to provide a
temporary fix, i.e. deleting HPC or restarting browser.
I have upgraded to Chrome 29 and found no difference really (although the
omnibox has a new look).
How can we help debug this?

chro...@googlecode.com

unread,
Jul 24, 2013, 4:20:06 PM7/24/13
to chromi...@chromium.org

Comment #121 on issue 178705 by demono...@googlemail.com: Address bar
Restarting Chrome does fix the problem for a while but the lag will almost
certainly build up over time. It doesn't seem to take as long as some
people have suggested, for me it will likely be an annoyance by tonight and
unbearable tomorrow.

I don't see any really long urls, and I'm not running the suggested
extension.

I'm running the following extensions:
AdBlock
Chrome Remote Desktop
Edit This Cookie
Google Quick Scroll
LastPass
NetBeans Connector
TooManyTabs for Chrome
View Link in Google Cache

I have just disabled a few others that I've not used for ages. I doubt any
of them would be causing trouble but if it appears otherwise then I'll
provide feedback.

Kallum

chro...@googlecode.com

unread,
Jul 25, 2013, 11:45:23 AM7/25/13
to chromi...@chromium.org

Comment #122 on issue 178705 by demono...@googlemail.com: Address bar
Yep, the lag has become unbearable again, >250ms...
It appears to be different for different strings though, for example all
the numbers I've been provider were when using 'chro', which is now
providing me with ~65ms. However, I noticed as typing facebook that I got a
major delay so I tried with 'face' and it gives me the 250ms mentioned
above. What kind of details should I provide now knowing it's really laggy,
histograms? "chrome://omnibox/" details?

chro...@googlecode.com

unread,
Jul 25, 2013, 2:45:44 PM7/25/13
to chromi...@chromium.org

Comment #124 on issue 178705 by demono...@googlemail.com: Address bar
'face' string is taking around 270-280ms at this point. PreFace.txt was
taken (although I have typed face in a few times previous obviously) and
then I did the 'face'-escape-'face'-escape thing around 10 times and
recorded PostFace.txt.

Kallum

Attachments:
PreFace.txt 18.0 KB
PostFace.txt 18.5 KB

chro...@googlecode.com

unread,
Jul 25, 2013, 3:01:44 PM7/25/13
to chromi...@chromium.org

Comment #126 on issue 178705 by demono...@googlemail.com: Address bar
Nothing but the ordinary 'facebook' I think...

chro...@googlecode.com

unread,
Jul 25, 2013, 3:31:43 PM7/25/13
to chromi...@chromium.org

Comment #127 on issue 178705 by mpea...@chromium.org: Address bar
I think at this point about:omnibox might help. Try both "f" and "face".
Please check all three Display Parameters boxes.

Also, have you searched for "facebook" a lot? (The histograms show that
the omnibox component that suggests queries is the slow piece for you, and
the only part of that I'm aware of in it that can be slow is the
queries-from-history part. That's why I'm asking these questions.)

chro...@googlecode.com

unread,
Jul 26, 2013, 6:45:05 AM7/26/13
to chromi...@chromium.org

Comment #129 on issue 178705 by demono...@googlemail.com: Address bar
I have the about:omnibox details for you. Taking a quick look, I now
realise that facebook has come up in my searches recently as I was
developing a website. However, up until this month I've had years of
history just saved up and never had Chrome run this slow. Now I just have a
few days worth of history.

Kallum

Attachments:
f.htm 79.2 KB
face.htm 78.8 KB

chro...@googlecode.com

unread,
Jul 27, 2013, 10:09:20 AM7/27/13
to chromi...@chromium.org

Comment #130 on issue 178705 by demono...@googlemail.com: Address bar
Just had to restart Chrome as serveral queries were at >1000ms and also an
update install was pending. I took about:omnibox and histograms before and
after restart for string 'face' though I'm not sure if you need them.
It seems like a lot of ui work for the onmibox (search query staying there
instead of the google url) and new tab page has come through in this
update. I'd like to hope that these changes are going to speed things up
but it's more likely that these updates (and the build up to them) are
causing the slow downs.
I'll provide feedback/debugging whenever you ask, or in 2 days time (when
it's likely I'll see whether the slow downs still occur) if nothing happens
in the thread.

Attachments:
face-preRestart-aboutOmnibox.htm 78.7 KB
face-postRestart-aboutOmnibox.htm 53.2 KB
face-PreRestart-histograms.txt 24.6 KB
face-PostRestart-histograms.txt 3.7 KB

chro...@googlecode.com

unread,
Jul 27, 2013, 3:46:00 PM7/27/13
to chromi...@chromium.org

Comment #131 on issue 178705 by Nick.Hoo...@gmail.com: Address bar
I just wanted to chime in here and say that I'm experiencing a very similar
issue. The omnibox is very (VERY) slow to record keyboard input. For
example, I can type the string "google" into the omnibox in under a second.
However, after I finish typing, I have to sit around for about 5 seconds
waiting for the keyboard input to painfully show up letter by letter in the
omnibox.

I'll keep an eye on this thread and see how it develops. Let me know if any
more specific information would be helpful. (Windows 8, Chrome Version
28.0.1500.72)

chro...@googlecode.com

unread,
Jul 29, 2013, 11:25:37 AM7/29/13
to chromi...@chromium.org

Comment #132 on issue 178705 by superk...@gmail.com: Address bar (Omnibox)
Well I experienced this problem also (about 30sec for the first 3 chars
entered !). Luckily, just disabling the extension 'HTTPS Everywhere' solved
immediately the problem without clearing anything or restarting chrome (of
course). I thank you myself for solving my problem and you all for your
efforts, because slow ominibox is evil ;)

chro...@googlecode.com

unread,
Jul 29, 2013, 11:42:06 AM7/29/13
to chromi...@chromium.org

Comment #133 on issue 178705 by ma...@schoenthaler.org: Address bar
I'll add to this that I've disabled all extensions and still experience the
issue on my home computer. It takes 20-30 seconds for the box to catch up
to my typing when I've typed several words.

The exact same version of Chrome on my work machine works perfectly fine.

chro...@googlecode.com

unread,
Jul 29, 2013, 11:57:06 AM7/29/13
to chromi...@chromium.org

Comment #134 on issue 178705 by demono...@googlemail.com: Address bar
After using Chrome for years, and no change in extensions for many months,
this has only just started being a problem. The main thing that's changed
my end is Windows 8. I've noticed many people posting here are also on
Windows 8. I've tried W7 compatibility mode but it doesn't help.

Some things that have changed on the Chrome side of things seem to be the
metro mode (which I actually got stuck in and I had to edit the registry to
escape it...) and the updated omnibox that displays a search instead of a
URL.

chro...@googlecode.com

unread,
Jul 30, 2013, 12:39:17 AM7/30/13
to chromi...@chromium.org

Comment #136 on issue 178705 by clay...@littlepiggiesgreencleaning.com:
Address bar (Omnibox) typing is awfully slow
http://code.google.com/p/chromium/issues/detail?id=178705

I had windows 7 before also and it worked flawlessly. I wonder if Microsoft
implemented code in widows 8 that purposefully causes problems with chrome
in an attempt to get them to switch browsers? Come on, I'd put something
like that in their court.

I also got stuck in metro mode as well. I blame windows 8 more than
anything. It's terrible lol

chro...@googlecode.com

unread,
Jul 30, 2013, 6:42:18 AM7/30/13
to chromi...@chromium.org

Comment #137 on issue 178705 by demono...@googlemail.com: Address bar
Just out of curiosity, I wonder whether the omnibox still slows down while
in metro mode. I don't dare try though in case I get stuck again...

Also, while it could be Microsoft, Firefox remain fine (although it has a
smaller userbase and thus is less likely to attract this kind of stuff from
MS). The onus has to be on the Chrome team to figure this out...

I've been using W8 since it came out (free copy as student...) and I'm
fairly sure this has only started recently, i.e. since an upgrade to W8.1.

chro...@googlecode.com

unread,
Jul 30, 2013, 3:01:40 PM7/30/13
to chromi...@chromium.org

Comment #140 on issue 178705 by demono...@googlemail.com: Address bar
I often have 30+ tabs across several windows so it could be tab related.

chro...@googlecode.com

unread,
Aug 3, 2013, 3:08:30 AM8/3/13
to chromi...@chromium.org

Comment #141 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
I am on Windows7, I doubt a bit this is Win8 only as when I was looking
into solutions I noticed old threads where people did mention having win7.

chro...@googlecode.com

unread,
Aug 6, 2013, 11:33:32 AM8/6/13
to chromi...@chromium.org

Comment #144 on issue 178705 by ivancmro...@gmail.com: Address bar
Hi all... would just like to say that I, too, had this issue and deleting
the History Provider Cache file helped. (I just did it).
Omnibox search is working fine, but I'll have to check back at the end of
the day to see if the changes persist.
Thanks for this suggestion!

chro...@googlecode.com

unread,
Aug 6, 2013, 1:12:38 PM8/6/13
to chromi...@chromium.org

Comment #145 on issue 178705 by ivancmro...@gmail.com: Address bar
Update to comment above:
Didn't even last 2hrs. It's slow again :(

chro...@googlecode.com

unread,
Aug 8, 2013, 8:39:04 AM8/8/13
to chromi...@chromium.org

Comment #147 on issue 178705 by mihai.ci...@gmail.com: Address bar
Having the same problem (slow autocomplete/search in the address bar), on
Windows XP.
Switching to other browsers until this problem is fixed...this is a show
stopper for me.

chro...@googlecode.com

unread,
Aug 8, 2013, 1:09:14 PM8/8/13
to chromi...@chromium.org

Comment #148 on issue 178705 by NICHOLAS...@YAHOO.COM: Address bar
I've been dealing with this issue for a year now. Just like a lot of
previous people have mentioned, I leave Chrome open for days (sometimes
weeks) at a time. I think this is the key to the issue.

Usually about 8 tabs open at any given time. Opening new tabs gives me no
delay. It's just waiting for the words to show in the Omnibox after I've
typed anything. Typing "Google" took 10.4 seconds beginning to end.

If my computer reboots, Chrome moves quickly again for about 3 days then
slows to a crawl again. I'm running Windows 7 and my system moves very
quickly and my Chrome is completely updated.

chro...@googlecode.com

unread,
Aug 9, 2013, 10:25:11 AM8/9/13
to chromi...@chromium.org

Comment #149 on issue 178705 by NICHOLAS...@YAHOO.COM: Address bar
Okay, So I found someone who resolved this issue themselves. They didn't go
into detail but if someone can break this into simple terms, apparently he
fixed it months ago and its still working well.

He said: "It'll take me like 25 minutes to remember and type it out
step-by-step, so I'll give you a general overview: I made a new Default
profile, hunted down and copied over everything I wanted (history files,
extension config files). The history is all in the profile root, the
extension config files are mostly in Local Storage with a few of them
spread out in other folders like databases and IndexedDB."

chro...@googlecode.com

unread,
Aug 10, 2013, 7:43:24 AM8/10/13
to chromi...@chromium.org

Comment #150 on issue 178705 by ma...@lodgify.com: Address bar (Omnibox)
I am reporting that this issue also affects our windows server 2012 too
(and there is no sleep mode there).
This is unacceptable and we are banning Chrome from our company as Firefox
seems to be a much more stable browser.
The Chrome team seems to not be able to put the correct priority to the
important bugs like this one.

chro...@googlecode.com

unread,
Aug 10, 2013, 7:44:45 AM8/10/13
to chromi...@chromium.org

Comment #151 on issue 178705 by marcodeg...@gmail.com: Address bar
(Omnibox) typing is awfully slow
http://code.google.com/p/chromium/issues/detail?id=178705

I am reporting that this issue also affects our windows server 2012 too
(and there is no sleep mode there).
This is unacceptable and we are uninstalling Chrome from our company as

chro...@googlecode.com

unread,
Aug 14, 2013, 12:43:05 PM8/14/13
to chromi...@chromium.org

Comment #153 on issue 178705 by mpea...@chromium.org: Address bar
> switch the omnibox search to bing and it is much faster. I don't like
> bing as well but until this gets fixed, I'll be using bing.

Interesting.

For the rest of you who experience the problem that the omnibox becomes
slower over time, can you try switching your default search engine to
bing the next time you notice the slowness and tell me if it helps?
Do _not_ restart Chrome after switching, just switch, tell me if the
lagginess goes away, and switch back and tell me if the lagginess
comes back.

I take this issue very seriously. I (and the people I've asked to
help) have not been able to reproduce it. We'd really appreciate
it if someone is willing to share a profile that experiences this
problem. I promise to keep it extremely confidential.

For what it worth, the "History Provider Cache" issue
(mentioned in earlier comments) has been fixed for Chrome 29.
So for many of you on Chrome 28 (the current stable channel),
this problem will probably mostly go away when the next
stable channel update happens. If you're on Chrome 28 and
want to see this fixed now, you can run the steps in comment
#96 to refresh the cache file. (This is probably what Nicholas
reported his friend doing in comment #149 that ended up
fixing the problem for him.)

thanks,
mark

chro...@googlecode.com

unread,
Aug 14, 2013, 3:12:13 PM8/14/13
to chromi...@chromium.org

Comment #154 on issue 178705 by eric.way...@gmail.com: Address bar
Mark

I have the same problem myself. Chrome 28 on Win 8 Pro x64 6 GB ram.

Mark I just tried what you wanted. I just over to bing as the default
search provider, did not close the browser. I just closed the settings
tab, open a new tab and typed away, and the omni box flew by and it could
keep up with my typing. It was nice and fast.

I then closed that tab, open the settings tab again, made Google the
default, closed settings tab, open new tab and instant slow down while
typing in the omnibox.

I haven't closed down chrome yet. I usually have it running for long
periods of time. When not using the computer I set it to Hibernate. When
it comes back I keep browsing as usual with all my tabs opened.

Another note, I have deleted the History Provider Cache file, and that
worked for a very short time. I don't remember the before size but I
believe it was a lot bigger than it is now. Right now its 41 KB, though my
History Index 2013-08 file is 4024 KB in size.

I'll attach a before and after file from the about Histograms also.



Attachments:
before.txt 1.8 MB
after.txt 1.8 MB

chro...@googlecode.com

unread,
Aug 15, 2013, 9:48:02 PM8/15/13
to chromi...@chromium.org

Comment #157 on issue 178705 by rpglov...@gmail.com: Address bar (Omnibox)
I tried transitioning to a search engine other than bing and it didnt help
much. is it just bing specifically?

chro...@googlecode.com

unread,
Aug 18, 2013, 9:02:07 AM8/18/13
to chromi...@chromium.org

Comment #158 on issue 178705 by apwe...@gmail.com: Address bar (Omnibox)
mpearson, tried turning off the prediction service, did not help.

chro...@googlecode.com

unread,
Aug 18, 2013, 3:28:25 PM8/18/13
to chromi...@chromium.org

Comment #159 on issue 178705 by clay...@littlepiggiesgreencleaning.com:
Address bar (Omnibox) typing is awfully slow
http://code.google.com/p/chromium/issues/detail?id=178705

Switching to Bing search solved problem immediately without restarting
browser

chro...@googlecode.com

unread,
Aug 19, 2013, 12:08:42 PM8/19/13
to chromi...@chromium.org

Comment #160 on issue 178705 by KevinDTa...@gmail.com: Address bar
When I switched back to Google, it was faster also, but slowed down again
pretty quickly. Let me know if I can help.

chro...@googlecode.com

unread,
Aug 20, 2013, 12:03:29 PM8/20/13
to chromi...@chromium.org

Comment #161 on issue 178705 by mpea...@chromium.org: Address bar
> Let me know if I can help.

I would love help! I'm still not able to reproduce this on my own. I'd
greatly appreciate if any of you are willing to give me a copy of your user
data. I promise to keep it in strictest confidence and only use it to the
extent needed to reproduce and identify the cause of the lagginess. Please
e-mail me directly at my username at chromium.org or at google.com.

Another question while I have everybody's attention:
- what is your startup page set to? (the new tab page? restore last
session? load these URLs?)
- what is your default search engine? (before you switched it to bing?)
Is it listed as {google:baseURL}search?q...
I'm particularly curious to know if all of you have a google URL (e.g.,
google.com) as a startup page and also google as the default search engine.

thanks,
mark
It is loading more messages.
0 new messages