[OSX-Users] Re: Time-outs with Chrome on OS X 10.8.2 at ECS (Building 32)

[Tim Chown]

Well, no IPv6 there... sadly.

--
Tim

On 22 Nov 2012, at 16:18, Michael Jewell <moj at ecs.soton.ac.uk> wrote:

> Aha! I think I may have just had this very same issue (while demoing a site, in fact), but on the eduroam wlan. I was also using Chrome on a MacBook Pro, and was trying to get to my internal server (tina.ecs). 
> 
> Cheers,
> Mike
> 
> On Thu, Nov 22, 2012 at 3:25 PM, Tim Chown <tjc at ecs.soton.ac.uk> wrote:
>> Well, I'd observe that those google and facebook sites have public IPv6 addresses advertised, and the UG lab has IPv6 to the workstations.
>> 
>> BUt the recent Chrome builds should try both IPv4 and IPv6 and use whatever works first, indeed OSX is quite reactive to find the right protocol to use.
>> 
>> Try an inconfig and netstat to dump host interface and routing information. Try a tcpdump to see what traffic is, or isn't, flowing.
>> 
>> Tim
>> 
>> On 22 Nov 2012, at 14:51, electronic Max <emax at ecs.soton.ac.uk> wrote:
>> 
>> >
>> > Hello,
>> >
>> > I am experiencing the worst, most frustrating kind of Heisenbug that is difficult to debug - I can't tell if it's a problem with Chrome, OS X, or even my hardware, but was wondering if any of you might have any insight or ideas I can try -- it's driving me crazy!
>> >
>> > What happens is that web pages often take a very long time to load at labs, pausing at the "Waiting for <host>" and eventually timing out.  Some 10% of my total page loads time out completely (ERR_TIMED_OUT) - others just take more than 15s to connect (which feels like an eternity)  THis seems to happen sporadically, worse at certain times of the day (like right now- peak lab times) and better early in the morning or late at night.  I noticed that the sites that I access and time out most often are : Google.com, Google.co.uk, Gmail.com and Facebook.com although these just happen to also be the sites that I test-access most often.
>> >
>> > Now, the real mystery is : I ONLY witness this behaviour at labs (building 32 ethernet).   It's very pronounced because the network here is so fast, so when something just spontaneously fails to load it's very noticeable.   This problem does _not_ happen at all when tethering over 3G or at home via DSL - at all, as far as I can tell.
>> >
>> > I cleared caches, created new profiles, tried different Chrome versions, to no avail.  I checked my Ethernet settings, frame size, DNS servers (I'm trying Google's DNS servers right now, 8.8.8.8 and 8.8.4.4) with no difference. I've removed all my Chrome extensions, tried launching chrome with built-in Flash disabled, cache disabled, still to no avail - and reverted all about:flags to default. Right now all of the above are disabled and it's still happening.
>> >
>> > I noticed that the sites I'm connecting to are nearly all SSL - could it be SSL related?
>> >
>> > I tried connecting through VPN and it seemed to improve things at first, but I can now confirm it still does the problem
>> >
>> > Cursory testing with Safari or Firefox do not exhibit the same symptoms, although I could merely not be using Safari or Firefox enough to run into the problems.  Chrome is my main browser, and I really need this to quit acting so annoyingly.
>> >
>> > If you have any thoughts pls do let me know
>> >
>> > thanks,
>> > Max
>> >
>> >
>> 
>> -- 
>> Dr Michael O. Jewell
>> ECS, University of Southampton
>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/osx-users/attachments/20121122/88728c42/attachment.html