When will Google fix the Chrome wi-fi bug?

I’ve been using Linux on the desktop (and laptop) since about 2003, and I’ve seen it progress from being something that didn’t work with most of the hardware I had access to (including the modem on my first laptop) to something that works without incident with most of what I use (although wi-fi is the most likely to be a problem, still). When I first used it, font rendering was its biggest drawback; these days, it has the best of any major operating system including Mac OS X (on which text looks dreadful on non-Apple monitors, including mine). Recently, a bug has appeared in Chrome, which will soon become the only show in town as far as general-purpose Linux web browsers are concerned (when Adobe stops supporting Flash on Linux except through Chrome) which makes it unusable on wi-fi: that it just stops loading anything.

This has been an intermittent problem on Linux for several months: use Chrome on Linux over a wi-fi connection and after a while it will refuse to load any page (despite appearing to try and load it for a minute or so), and tell you it cannot find it or that you are offline. Other network apps, like Thunderbird and, significantly, Firefox, will continue to work. It continues to work if you use Chrome in Incognito mode as well. After a few minutes it will mysteriously start working again. This has in the recent past led me to wonder if it was not the wi-fi that was the problem (and to turn it off and back on again); since starting to use a Mac laptop regularly (and since a friend who recently installed Linux on her laptop complained about the same problem), it has become obvious that it isn’t, because other people (and my Android phone and tablet) continue to be able to access the web normally.

I’m not sure if this is a regression which has happened in Chrome recently or has been there for years, but we got our Virgin wi-fi router a few years ago and I know I haven’t always been having this problem, and it’s got markedly worse in the last few months. I attempted to fix it this afternoon by disconnecting it from my Google account, but after this it simply refused to load anything, stalling at “Waiting for cache” (again, incognito mode and all other apps worked fine), and then deleting my entire Chrome config directory (same result). In short, this app isn’t working and is rendering Linux as a networking platform useless. As Firefox will come to the end of its useful life on Linux later this year, and as many Linux users use it on laptops and access the Internet over a wi-fi connection, this bug really needs fixing urgently.

Possibly Related Posts:

  • And there I was thinking the “waiting for cache” nonsense was attributable to (1) lack of RAM on my laptop; (2) using privacy badger; (3) using adblock plus; (4) using https everywhere; (5) using referrer control, or some odd combination of all of the above! Suffice to say, I disabled all above stated extensions and STILL the problem persists, in which case I was blaming lack of RAM on this box.

    Upon further investigation and experience, I’ve been noticing this problem occurring over three different operating systems -Win7, Ubuntu and Linux Mint. When I checked the Google Chrome forum it was filled with Win7/OSX users complaining about the same problem as far back as 2009 with nary a peep from Google. Just page after page of complaints. Chrome is so amazing that Google evidently does not feel the need to even acknowledge an issue with it.

    Further, Chromium doesn’t seem to be much better. I stopped using it because flash crashed constantly and video was problematic. So far, the silence from Google regarding this problem has been ::DEAFENING::