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.
dont you wanna report that message bug too :p
One at a time. If it repeats. Right now, this one is frustrating the hell out of me. :/ One goddamn page of laTex in that integral problem!!- feels like crap right now :/
safari for windows does that too...in a way
Yeah :/ Makes me contemplate suicide lol.
go skydiving and *forget* to wear the parachute
Disappointing that it's two days, and yet no acknowledgment from any admin. :/ @mattfeury and @farmdawgnation and @shadowfiend
The OpenStudy tab did not crash, all of your Chrome tabs crashed. I'm afraid that's not a problem with OpenStudy, so there's nothing we can do about it.
Since you have a TED talk open, it is not at all unlikely that the cause of the crash was the Flash plugin, but only the Chrome folks will know with any certainty. For ourselves, the crash we attended to only crashed OpenStudy tabs, and was due to a very specific issue with Chrome's handling of sorting. That bug has been fixed in Chrome, and therefore no longer manifests on OpenStudy.
@shadowfiend - am sorry, but if you look carefully, all the tabs did not crash. The third tab (which has been shaded) did not crash, and still has that 'g' logo visible. I received that TED link in OpenStudy chat, and it crashed along with the OS tab. This is not something new, I had noticed this problem of other tabs (whose links I clicked through OS) crashing along with the OS tabs, even before the bug was solved. And also, it did not happen soon as I clicked the TED link. The TED tab had been there for a good 15-20 minutes, so I think that rules out the probability that the flash plug-in was a cause behind this. Also, this was not the first time this happened since the issue was 'claimed' to be fixed. It crashed a couple of times more, about a week or so back. Another thing that I have noticed (may or may not be useful) is that it generally crashed/crashes when there is a lot of LaTeXing being done. Admittedly, the crashes have gone down by 90%, but then, when you assume it's not going to go down, and lose a lot of work when it does, it's extremely frustrating. So, would help if you could kindly have a look at it. Thanks :)
Let me put it differently: if Chrome is experiencing a crash, that is not a problem with OpenStudy, it is a problem with Chrome. If we can find the crash, we can report the bug to the Chrome folks. However, not only have we not seen the crashing you're talking about, but it's taking down more than just the OpenStudy tab, which indicates it isn't even necessarily a problem with how OpenStudy itself is operating.That makes it doubly difficult, because it means there's no guarantee that we'll even get the tab crash to happen ourselves just by using the site for long enough; there is more at play. If we spot the crash, we'll do what we can, but the best thing you can do right now is try to report this issue to the Chrome folks, I'm afraid.
I haven't experienced any chrome crashes at all ever since that huge OS update about 2 weeks ago. I didn't update Chrome or anything. The lagging stopped and now everything is just fine. Previously OS would lag even though no other site would lag. OS said it wasn't related to the site, but based on the fact that I did nothing to fix the problem and the problem fixed itself after an OS update, I'd say that somehow OS was related to Chrome Crashes since they only happened when I was logged into OS. On top of that, the weirdest thing of all is that when Chrome Crashed, only the OS tabs would crash with an "Aw Snap". None of the other tabs would crash. I'd say OS needs to re-evaluate their assumption that the crashes are not OS related.
We have never claimed that those crashes were not *related* to OS, we stated that they were not our *fault*. @farmdawgnation then meticulously debugged the issue for the Chrome team and helped them fix the bug IN CHROME that was causing these crashes, a bug that was in an absurdly basic part of their software. You would have to hand me hard evidence that you didn't update Chrome (like a version number that is below the one with the relevant fix), since it turns out that Chrome updates in the background for you, so if you've so much as restarted the software since then, you have updated Chrome. Last but not least, we have never claimed that the site slowness is not related to OS either. We have in fact freely acknowledged that there are performance issues, while admitting that we don't experience them as much because we have faster machines. We have moreover worked hard to mitigate those issues over the past few months. I understand that this is the first time you have expressed the point of view that we don't consider certain bugs to be related to OS, but you are not the first one, and I want to put this to bed. We have never expressed that any behavior that only happened on our site was unrelated to our site. We take every report seriously and, when we can reproduce it, we try to address the underlying bugs. When the underlying bugs aren't ours but the browser's, we *still* try to work with the browser makers to get the relevant issues fixed, or, if that's not possible, we work around the issue. I hope that clarifies our stance on issues you may experience when on OpenStudy.
Wow @farmdawgnation , I didn't know you fixed Chrome's own bug. I may have been wrong but it motivated you to let me know what really happened. I appreciate it.
Thanks, but credit where it's due: I simply went digging around until I had enough information for the Chrome team to do what they do best. Google has an excellent engineer who went spelunking in the V8 engine code to track down the issue in their array sorter. That said, do remember in the future that correlation doesn't imply causation. We don't say things like "this isn't a bug with our code" to pass the buck onto a different team. If we ever gave you the impression that's how we operate, I apologize, because it isn't. We work hard to engineer this site with as much precision as possible. If you could be kind enough to extend the benefit of the doubt towards us in these situations, it would avoid the need for long essays like the one shadowfiend just wrote. :)
Sure thing. I didn't mean to. Sorry. I just needed clarification.
Aye. No harm, no foul. :)
Okay then, thanks Shadow and farm, I'll write to the Chrome folks, and let them know about this issue, and if there's a particular problem in my case only, then let's find that out as well. Thanks.