What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 130 Stack Exchange communities.

If I'm chatting in...chat, I'm getting intermittent disconnects, with the following message:

There seems to be a problem connecting to the server. Please check your internet connection and reload this page.

I usually only get that if chat is down, but it's not: if I wait 30 seconds or do a hard refresh, the message goes away and it's like nothing's wrong.

Other issues include:

  • real-time being dropped: people will be talking, but I won't see their messages until I refresh the page
  • Loss of the audible bell for chat pings

This only just started happening yesterday: I've kept chat open nearly 24/7 for several months now with no issues coming close to this. But it's constant now: if I'm in chat for any length of time, it'll happen every few minutes.

I've tested this in Safari 5.1 and with Fluid.app (popular site-specific browser for OS X that uses the same engine Safari uses, just with some custom chrome) in OS X Lion.

Presumably this is related to the chat changes yesterday: we did some diagnosing in TL and thought it might be specific to Fluid.app, but even after switching to Safari full time it happens all the time.

Any ideas?

share|improve this question
1  
we have been playing with some infrastructure changes in this area... we're investigating. –  Marc Gravell Feb 21 '12 at 22:16
    
Technically I'm getting this as well, but it's infrequent. Chrome Current Normal Release btw. –  jcolebrand Feb 22 '12 at 0:19

1 Answer 1

up vote 5 down vote accepted

OK; we've identified this as an issue affecting Safari and a few older browsers, and have tweaked (aka disabled) a few things as a temporary fix. Short version: it should work like normal for now (for better or worse). I'll implement the proper fix after some sleep.

share|improve this answer
2  
It wasn't just "a few older browsers," it was doing the same thing with the latest version of Chrome today. –  Ward Feb 21 '12 at 23:57
    
@Ward yes, but that was actually a backlog etc caused by the older browsers (and my broken code). No, really. Actually, kinda related to my tweet earlier: twitter.com/#!/marcgravell/status/171959466449842178 –  Marc Gravell Feb 22 '12 at 0:00
    
FWIW, it just did it again... Test procedure: open a chat room in a new tab (in this case, ServerFault Vote to Close). Wait a while, check on the tab, read something in another tab for a while longer, check the tab - yep, error message displayed. –  Ward Feb 22 '12 at 0:04
    
Also FWIW, it's been working just fine in Safari and Fluid.app for the past 30 minutes or so. –  user149432 Feb 22 '12 at 0:23
    
@Ward k, I'll try that, but; I've been doing similar all day. Can I ask - what is your OS etc? –  Marc Gravell Feb 22 '12 at 6:31
    
XP Pro, all current updates, Chrome 17.0.963.56 m, DSL connection both places I've been today. Hasn't done it in testing just now. –  Ward Feb 22 '12 at 7:09
    
@MarcGravell Well, it was working great for several hours yesterday, but now it's back to the same thing in Safari and Fluid: disconnects and lag every few minutes. –  user149432 Feb 22 '12 at 19:57
    
@Mark how odd; I don't have an OS X for testing... Darn. Working fine for me on iPad, though. Are you getting any error messages in the browser's debug tools? –  Marc Gravell Feb 22 '12 at 19:59
    
@MarcGravell Nothing: it'll look like the room died out, but when I refresh, I'll get all the messages I missed. Screenshot of what I see in the network tab when I load chat if that helps at all. Console is empty. –  user149432 Feb 22 '12 at 20:10
    
@Mark dammit... I wonder what it is trying to do! Initially I wondered if it was trying a ws-ping for latency, but it is using hixie-76, which doesn't support ping! Banging head on desk now... –  Marc Gravell Feb 22 '12 at 20:15
    
@Mark what I do know: I have had to add extra code to handle issues with lots and lots of hixie clients who disconnect improperly; but iPad etc is hixie-76 and works perfectly –  Marc Gravell Feb 22 '12 at 20:18
    
@Mark are you behind a proxy? Maybe your proxy hates web-sockets... –  Marc Gravell Feb 22 '12 at 20:22
    
@MarcGravell Hah. Is there any other debugging information I can provide? I have a packet dump, if that'll help. I'm not behind a proxy, and chat seems to work swimmingly in Chrome on my computer. –  user149432 Feb 22 '12 at 20:26
    
Packet dump a twist you are sockets.or might help... Only if you have time –  Marc Gravell Feb 22 '12 at 20:56

You must log in to answer this question.