Quote:
Originally Posted by KC911
I see where the rollout of Chrome 58 started havoc on many platforms beginning May 2...
I'm on Chrome 42.0.2311.111
|
Yeah, was just finishing up a project for a client.
Turned them lose to beat up the backend and stress test it.
Everyone in the office was getting the oh snap but no one outside the building.
Even if someone took their laptop home, the problem went away.
Managing Director is beating me up to "fix" the back end.
4 days of back and forth to get him to understand I can't go to every person on the face of the planet that might hit this thing and make sure THIER computer, network, or whatever was configured correctly.
Has nothing to do with what I built but what they were using and where they were using it from to access what I built.
I suspect the issue is their firewall in the building.
I nearly posted here to have you guys beat it up to see how pervasive the issue might be in the real world but we resolved it.
The oh snap is too generic an error because there are literally dozens of things that can trigger it and sometimes it's a combination of several of them.
Chrome needs to do a better job of explaining why it farted.