搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

iGoogle will not load completely

  • 2 个回答
  • 10 人有此问题
  • 1 次查看
  • 最后回复者为 theoldwizard1

more options

Since installing Firefox 5.0, iGoogle will not finish loading (or takes more than 5 minutes). IE8 loads iGoogle normally. Firefox 5.0 load Google immediately.

While waiting for iGoogle to finish load there is a status box that says "Read www-opensocial.googleusercontent.com". If you open another tab and go to that URL it says "Error 404 not Found".

Problem has been reported to Google Help forum (http://www.google.com/support/forum/p/Web+Search/thread?tid=0cef36810af2587e&hl=en)

Erasing all cookies and history does not resolve the problem.

Re-installing Firefox 5.0 does not resolve the problem.

Since installing Firefox 5.0, iGoogle will not finish loading (or takes more than 5 minutes). IE8 loads iGoogle normally. Firefox 5.0 load Google immediately. While waiting for iGoogle to finish load there is a status box that says "Read www-opensocial.googleusercontent.com". If you open another tab and go to that URL it says "Error 404 not Found". Problem has been reported to Google Help forum (http://www.google.com/support/forum/p/Web+Search/thread?tid=0cef36810af2587e&hl=en) Erasing all cookies and history does not resolve the problem. Re-installing Firefox 5.0 does not resolve the problem.

所有回复 (2)

more options

This problem is intermittent, but occurs frequently.

Re-installed FF5 after manually deleteing all caches and cookies. Short term fix (Problem returned next FF5 session).

Reset iGoolge. Short term fix (Problem returned next FF5 session).

Problem does NOT occur when I go to www.google.com or logout of iGoogle and the go to www.google.com/ig.

Problem does not occur on IE8.


Add-ons include Adblock Plus, Microsoft .NET framework and AVG Safe Search (disabled)

Sometimes I get "Waiting for www.google.com..."

more options

The problem turned out to be a bad interaction between the iGoogle Finance gadget and the AVG LinkScanner.

The solution was to turn off LinkScanner.