Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

FF 13.0.1 hangs with Google, other browsers do not

  • 2 ŋuɖoɖowo
  • 7 masɔmasɔ sia le wosi
  • 1 view
  • Nuɖoɖo mlɔetɔ lkaven

lkaven
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.

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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.

lkaven
lkaven Biabia la
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 trɔe