為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

FF 13.0.1 hangs with Google, other browsers do not

  • 2 回覆
  • 7 有這個問題
  • 1 次檢視
  • 最近回覆由 lkaven

more options

When attempting to do an ordinary google search under FF 13.0.1, from the google.com home page, FF will hang indefinitely with no status message. This is on Vista SP2, but also happened on my friend's Macbook, also with FF 13.0.1.

This happens when 'live search' is set up. No live search results will pop up, indicating live search inaccessible. Click "search" and nothing happens. There are no messages for looking up, connecting, waiting, transferring. The browser just hangs. Will usually respond to a dismissal, but not always.

Google news will load display as always. But it will hang when you try to search within news.

When I switch to Safari, everything works.

When attempting to do an ordinary google search under FF 13.0.1, from the google.com home page, FF will hang indefinitely with no status message. This is on Vista SP2, but also happened on my friend's Macbook, also with FF 13.0.1. This happens when 'live search' is set up. No live search results will pop up, indicating live search inaccessible. Click "search" and nothing happens. There are no messages for looking up, connecting, waiting, transferring. The browser just hangs. Will usually respond to a dismissal, but not always. Google news will load display as always. But it will hang when you try to search within news. When I switch to Safari, everything works.

所有回覆 (2)

more options

You can check the network.http.* prefs on the about:config page and reset all bold user set network.http prefs to the default value via the right-click context menu -> Reset.

You can also try to set the Boolean pref network.http.spdy.enabled to false on the about:config page.

more options

On your advice, I did toggle network.http.spdy.enabled to false. I also did find that network.http.keep-alive was /user-set/ to FALSE. I reset this to TRUE. After these two changes, things work again.

Funny thing was, I never did change the keep-alive parameter, and don't know what might have changed that.

Watching and waiting. Very grateful for the remote help from Krypton.

Luke

由 lkaven 於 修改