Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Why is searching with the awesome bar so slow?

  • 2 odpowiedzi
  • 34 osoby mają ten problem
  • 21 wyświetleń
  • Ostatnia odpowiedź od cor-el

more options

recently i noticed that when i tried searching for something using the awesome bar, it was a whole lot slower than searching with the search bar. this happens every time.

i also tried searching with the awesome bar using firefox's keyword search where i put google's keyword as simply "g". so if i wanted to search for let's say "computer" on google, i type "g computer" in the awesome bar, hit enter, and the google results comes up almost instantly. but if i just type in "computer" the page takes much much longer to load!

is it just me or is this a common problem? any fix for this?

recently i noticed that when i tried searching for something using the awesome bar, it was a whole lot slower than searching with the search bar. this happens every time. i also tried searching with the awesome bar using firefox's [http://bit.ly/hXeaTi keyword search] where i put google's keyword as simply "g". so if i wanted to search for let's say "computer" on google, i type "g computer" in the awesome bar, hit enter, and the google results comes up almost instantly. but if i just type in "computer" the page takes much much longer to load! is it just me or is this a common problem? any fix for this?

Zmodyfikowany przez yeungb w dniu

Wszystkie odpowiedzi (2)

more options

Any updates here? I can confirm this only happens when you don't lead with 'g' and that it's not caused by bookmark/history search since it happens after you hit enter and the history drop down disappears. It also seems to speed up after the term / page you searched is cached.

I've played around with about:config Keyword.URL to no avail. Any ideas? Anyone not have this problem when they simply type "test" and hit enter?

more options

Are you keeping a large history?

Do you see a spinning favicon on the left hand side of the location bar when that happens?


This can be caused by a problem with the file places.sqlite that stores the bookmarks and the history.