搜尋 Mozilla 技術支援網站

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

了解更多

Firefox stops loading pages after a while.

  • 1 回覆
  • 45 有這個問題
  • 1 次檢視
  • 最近回覆由 Bobert51

more options

After using firefox for anywhere from 5 minutes to several hours, webpages stop loading for me. The icon on the tab just spins to the left and the tab says "connecting". However, even left for a half hour, it will never connect. Other browsers load pages fine when this happens, so it's not a connection issue. This has only started happening as of v7. If I restart firefox everything works fine again for a random amount of time. I have already tried a totally clean install, uninstalling and removing all traces of firefox from my system, so it's not an add-on issue. I have the latest version of flash. I'm out of ideas. I did restore backed up bookmarks after the clean install, but I can't possibly believe that a bookmark would be responsible for this.

After using firefox for anywhere from 5 minutes to several hours, webpages stop loading for me. The icon on the tab just spins to the left and the tab says "connecting". However, even left for a half hour, it will never connect. Other browsers load pages fine when this happens, so it's not a connection issue. This has only started happening as of v7. If I restart firefox everything works fine again for a random amount of time. I have already tried a totally clean install, uninstalling and removing all traces of firefox from my system, so it's not an add-on issue. I have the latest version of flash. I'm out of ideas. I did restore backed up bookmarks after the clean install, but I can't possibly believe that a bookmark would be responsible for this.

所有回覆 (1)

more options

https://support.mozilla.com/en-US/questions/881844#answer-254761

They seem to have an answer there, but I'm not sure exactly what effects the changes have (other than to make FF usable again). Since changing that value to 48, I haven't had it hang yet. Keeping my fingers crossed that it doesn't. This doesn't seem like a long term solution though. Hoping the kind devs at Mozilla are getting ready to release 7.0.2 fixing this bug.