8 replies to this topic

[Saduff]

I keep getting this error over time with Google Chrome:



When I get it, I have to reload the page a couple of times and
it will be back to normal, until it happens again (usually pretty soon).
It's most likely a Chrome bug, but this is the only site where this happens.
Anyone knows why this happens or has a solution?
I'm using Chrome v11.0.696.71 (dev channel).

[Teddy Rogers]

If you can tell me what time this occurs and which time zone you are located in I can check against the server logs to see if there is a problem at our end...

Ted.

[Saduff]

It occurs often over time. My time zone is UTC+3.
I'll switch over to the stable channel of Chrome and see if that helps.

-- EDIT --

Haha, the whole time I thought I was on the dev channel, but I was actually on the stable channel.
Now I switched to the dev channel (v13.0.782.1 dev-m), but this error still occurs.

Edited by Saduff, 03 June 2011 - 04:36 PM.

[Teddy Rogers]

I apologies but I completely forgot about chasing up your issue until I read it again this morning. I looked in to the matter and I think your problem may be related to your machine as described in the following thread because there appears to be no issues with the server...

http://www.google.co...203ffa292&hl=en

Ted.

[Saduff]

Thanks Ted, and no problem man.

I tried some of the solutions offered there, including WinsockFix, but it didn't help.
I'll try using Firefox for some time and see if it happens with Firefox as well.
Is no one on this board using Chrome, or no one has this problem?
If a Chrome user could tell me that he doesn't have this problem (and his Chrome version),
then I could know for sure that it's a problem on my end, and not a Chrome bug or a problem with the board.

Edited by Saduff, 11 June 2011 - 08:11 AM.

[Teddy Rogers]

I use Chrome (current stable release) occasionally and I have never experienced this so the problem either exists at a particular time when you are connecting which, I cannot deduce as being a cause from server logs or it is a problem at your end somewhere...

Ted.

[Saduff]

No problems when using Firefox.
I have now identified the root of the problem : Chrome extensions.
Have had no problems in Chrome incognito mode (all extensions disabled).
Now I have to find the conflicting extension and disable it.
I'll give you an update once I find it.

Edited by Saduff, 11 June 2011 - 10:15 PM.

[vic4key]

Hi Saduff, a long time no see again. I think GC (Google Chrome) very much error. I used & using it but now i'm installed more (GCP) Google Chrome Plus. GCP is good more GC. So i think u should use GCP replace GC. U can download it here. G.lucky to u!  
BR,

Edited by vic4key, 13 June 2011 - 05:54 AM.

[Saduff]

Thanks vic4key, looks interesting. I'll try it.
And I haven't found the extension yet.

Question : Do all Chrome extensions work with Chrome Plus?
Never mind, already got an answer to that.

-- EDIT --

Update : It appears that disabling all extensions doesn't fix it either.
The only thing that fixes it is if I use an incognito window.
Incognito window means that all extensions are disabled and it doesn't save any history.
Disabling all extensions in a regular window still produces this error though.

-- EDIT --

Yeah, Chrome Plus works great. Haven't got the error yet.
And I installed all the same plugins I had in Chrome.
Chrome Plus is better anyway.

-- EDIT --

Arrgh, why the hell did I get greeted by that error today?
I thought ChromePlus didn't have it, but it seems that Chromium is the problem.
Well, just need to get used to it, or start using the incognito window.

-- EDIT --

OK, now I'm getting this error on other websites as well.

Edited by Saduff, 14 June 2011 - 09:14 AM.