At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
KILL THE COOKIES
Wait, that solves nothing.
i thought they bugfixed it already? it still happens to you??
yea ! :-(
What is the reloading problem? What does reloading have to do with being online? We're fairly confident in our fixes to onlineness, but it's not 100% clear which issue you're talking about.
@shadowfiend Whenever I type any message , the necessity of reloading becomes prominent. Because I experience a lot of buffering , and Iam not even aware whether the message has been sent or not. A day ago, I was having a message talk with @FoolForMath , and I faced this buffering problem again. Infact FFM told me that he received my message multiple times , about which I had no idea at all. And talking about the "logging out" issue , what happens generally is that while Iam on OS , many a times the content on the current page vanishes , and again "reloading" happens. So even though I logout , I still remain online. Infact I checked my internet connection , but couldn't find as such any problem. Also because of this reloading problem , I generally lose the data which I had been typing during that time ( messages, answers, questions). Infact while typing this message, I faced the same problem again many times , so I had to make a backup copy of this reply. I'll check my internet connection again for sure , but on your part , please see if something could be done about it. Thanks ! :-)
We're aware of the message issue. It's annoying, but we're working on it. I still don't understand the second problem that you're talking about. "The content on the current page vanishes"? I need more details if we're going to debug this. Can you provide us with a screen shot? Also, do you see the "Connection lost" error message in the bottom left corner of the screen?
could you also answer why os keeps "aw snapping" in google chrome? (or whatever that term the blue screen says) @farmdawgnation
ohhh hearing back..that's good :)
The message issue was hopefully fixed. I suspect the multiple messages are related to people thinking it's still broken though. Messaging may take a while to send when the site is at high load, but if you hit send, it will get sent. Thinking that it's lagging and re-sending the message will do exactly what you would expect: send it multiple times. Sometimes it could go instantly, sometimes it could take up to 30s. Any longer than that, and there may be an issue, but by resending you're not "overriding" the previous message, just duplicating it.
@farmdawgnation I often experience "connection lost" error ( its written with red colour and is displayed in a yellow box)
@mattfeury But how would I come to know that my message has been sent or not ? Sometimes the message din't get sent , and sometimes , multiple times. And yea , the spinning cursor is really annoying.
@anjali_pant In regard to your first one, that definately shouldn't be happening. What browser and OS are you using? In regard to your response to @mattfeury - the problem is that your message has been sent, but your computer is waiting for confirmation. If you're having connection issues, these problems could be related.
@farmdawgnation Iam using google chrome
Yeah, then it's entirely possible you were having internet connection issues. Most of the team uses Google Chrome full time and we haven't seen any issues with the connection lost dialog appearing.
But then many were having "aww-snap" prob , so I don't think its an independent issue.
No, it's definitely an independent issue. I've seen the crash log. Something causes Chrome tries to access a memory address that doesn't exist in its address space while running our site, which is what causes the crash. That's definitely an issue that falls squarely in their court. :) That said, if they provide us with a work-around until it is fixed, we'll gladly implement it.
Ohk great ! And you people must be working together to solve it , right ?
If they ask for our help we'll gladly give it, but they haven't reached out. So they're handling it on their end. (I suspect we're not the first to report this bug.)
Oh ! Well I think that, now all I can do is , CROSS MY FINGERS ! :-(