Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Why is searching with the awesome bar so slow?

  • 2 respostas
  • 34 têm este problema
  • 21 visualizações
  • Última resposta de 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?

Alterado por yeungb em

Todas as respostas (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.