Google Reader Errors in 64-bit Safari 4.0.3

Question

Level 1

10 points

Google Reader Errors in 64-bit Safari 4.0.3

Since the update to Snow Leopard and moving to a 64-bit version of Safari (Version 4.0.3 (6531.9)), I have been experiencing a script error in GOOGLE READER ( http://www.google.com/reader/).

After several minutes of browsing, I receive an error message stating "Oops…an error occurred. Please try again in a few seconds." After the error, I can view currently loaded content, but attempts to view any additional content results in an empty folder and the following error: " "The feed being requested cannot be found." As a result, I am logged out of Google Reader and must log-in again. Interestingly, I am only logged out at the Google Reader site and can access other Google web properties without logging in.

I do not experience this error using Camino or FF, only Safari.

I've tried emptying the browser cache, restarting Safari and even resetting Safari. I've even tried using a secure page (https) instead of the traditional Google Reader URL. None of these have any effect. Error seems to be specific only to Google Reader on 64-bit Safari.

Any thoughts? Suggestions?

MacBook 2Ghz C2D 2GB Ram, Mac OS X (10.6.1)

Posted on Oct 9, 2009 5:00 PM

Reply

Answer 1

Oct 9, 2009 7:35 PM in response to txnole

Greetings,

Why don't you try running Safari in 32-bit mode to see if the problem persists? You're not gaining any real benefit by running 64-bit mode.

Reply

Answer 2

txnole Author

Level 1

10 points

Oct 10, 2009 6:10 AM in response to Golden Shoes

Yeah... I'll give that a shot, I suppose. Doesn't really speak to the underlying problem.

Reply

Answer 3

txnole Author

Level 1

10 points

Oct 10, 2009 7:04 AM in response to txnole

Nope. Just tried the under 32-bit mode and was logged out after pausing to read the contents of an article for less than 30 seconds. Same javascript error message in the header of the page.

Reply

Answer 4

Oct 10, 2009 7:32 AM in response to txnole

What is the exact text of the JavaScript error message? Have you tried creating a new User account and testing for this problem there? If not, you should do that.

Reply

Answer 5

txnole Author

Level 1

10 points

Oct 11, 2009 4:51 AM in response to Golden Shoes

The exact text of the errors are as before:
- "Oops…an error occurred. Please try again in a few seconds."
- "The feed being requested cannot be found."

I have tried deleting cookies, restarting, and logging in with another Google account. Same issue.
I *cannot* recreate the errors in Camino, Chromium or Firefox - only in Safari.

I note from your singature that you are using an older version of OSX.

Any SL users familiar w/ Google Reader that can offer troubleshooting or suggestions? I think I've hit the wall on what to try.

Reply

Answer 6

Oct 11, 2009 7:23 AM in response to txnole

"The feed being requested cannot be found."

If it happens in both 32-bit and 64-bit mode, but not another browser, that would seem to implicate the HTML and/or JavaScript being used by Google Reader is somehow incompatible with Safari, so it's not a Safari or Snow Leopard issue, unless you didn't have this same problem with the same feed in a previous version of Safari.

I note from your signature that you are using an older version of OSX.

Yes, but that makes no difference. Safari 4 is Safari 4, regardles of which version of the OS it's running on.

Reply

Answer 7

txnole Author

Level 1

10 points

Oct 11, 2009 7:28 AM in response to Golden Shoes

Golden Shoes wrote:
Safari 4 is Safari 4, regardles of which version of the OS it's running on.

I would agree, except that I didn't have an issue in Leopard on Safari 4 or Webkit.

The issue with being logged out makes me curious if there is some issue with the way SL is caching or handling cookies.

Reply

Answer 8

Oct 11, 2009 7:38 AM in response to txnole

The issue with being logged out makes me curious if there is some issue with the way SL is caching or handling cookies.

It could be a corrupt cookie, and you could test for that by quitting Safari, then deleting the Cookies.plist file from Home/Library/Cookies, relaunching Safari and see if you can replicate the issue. If not, then that would seem to be the actual cause of the problem.

Reply