Google Chrome Experiment Crashes Browser Tabs, Impacts Companies Worldwide (zdnet.com) 50
A Google Chrome experiment has gone horribly wrong this week and ended up crashing browsers on thousands, if not more, enterprise networks for nearly two days. From a report: The issue first appeared on Wednesday, November 13. It didn't impact all Chrome users, but only Chrome browsers running on Windows Server "terminal server" setups -- a very common setup in enterprise networks According to hundreds of reports, users said that Chrome tabs were going blank, all of a sudden, in what's called a "White Screen of Death" (WSOD) error. The issue was no joke. System administrators at many companies reported that hundreds and thousands of employees couldn't use Chrome to access the internet, as the active browser tab kept going blank while working. In tightly controlled enterprise environments, many employees didn't have the option to change browsers and were left unable to do their jobs. Similarly, system administrators couldn't just replace Chrome with another browser right away.
Chrome Browser for enterprise (Score:3, Insightful)
Re:Chrome Browser for enterprise (Score:5, Informative)
If you read the bug report thread many were using the enterprise edition. Unfortunately Google reserves the right to push many flags that are not explicitly in the control of the admins such as revoking ssl certs.
https://bugs.chromium.org/p/ch... [chromium.org]
> However, some components are exempt from this policy: updates to any component that does not contain executable code, or does not significantly alter the behavior of the browser, or is critical for its security will not be disabled.
https://getadmx.com/?Category=... [getadmx.com]
Re: (Score:3)
However, fixing the problem actually made system administrators even angrier. Many didn't know that Chrome engineers could run experiments on their tightly-controlled Chrome installations, let alone that Google engineers could just ship changes to everyone's browsers without any prior approval.
Seriously, who the fuck in Google thought this would be a good idea? That's beyond bad.
Re: (Score:2)
Re:Chrome Browser for enterprise (Score:5, Insightful)
Shouldn't they have been using Chrome Browser for enterprise with policies to prevent Chrome experiment from being inflicted on users?
https://cloud.google.com/chrom... [google.com]
You shouldn't be using spyware in enterprise anyway.
Re: (Score:2)
>implying enterprise everything isn't spyware
Re: (Score:2)
Re:Chrome Browser for enterprise (Score:5, Insightful)
"Hey, we're a multi-billion dollar company, but can't be bothered to test our software properly. If you could just roll out this beta to your internal corporate network and test it for us that would be aces. TIA luv da Goog"
Yeah. Bollocks to that.
Re: (Score:1)
It's not uncommon, and we have three waves, for companies to deploy updates in a rolling waves exactly so that we have a chance to pick up issues before they are widely deployed. This wouldn't have protected us in this case because we don't currently test browsers before full release, but you can bet we'll
Re: Chrome Browser for enterprise (Score:2)
What if I told you that Google are an enterprise, and that they could have tested the beta themselves.
#mindblown
Re: (Score:2)
This bug was present in all releases of Chrome for several months but was enabled to 1% of the systems, without notifications to the system admins, who just assumed they had some randomly glitching machines, then pushed to all Chrome installation, again silently and regardless of policies that sysadmins had control over. So this happened with no changes on the customers side, and rolling back to previous releases or doing full reinstalls did not undo the behavior. This is why so many people are so pissed. T
Re: (Score:2)
You test the vendors new software to make sure that your stuff works with it. You don't test their software to test for bugs in their code. It's doubtful that anyone doing testing of their company's software would have overlapped another window on top of the browser winder during testing on a beta version and triggered this response. And even then it was with specific versions of Windows which the testers might not be working with. I'm just saying that even if companies did test the beta that had the featur
Re:Changes on a whim, surprise surprise (Score:5, Insightful)
Actually this is a Google thing that has been infecting everyone. Prior to Windows 10, Microsoft Updates *never* changed a setting that the user had set. Unfortunately this "experiments" thing is also a part of Firefox, but at least in Firefox you can turn it off to prevent Mozilla from making random changes to your configuration. With Microsoft you just have to get used to it and write software to make sure that things stay as you set them (the worst offender being the Microsoft Firewall, which will adjust itself at every turn to allow all sorts of stupid little Microsoft shits (like the Calculator) receive unsolicited incoming connections from the Internet).
Re: (Score:2)
Prior to Windows 10, Microsoft Updates *never* changed a setting that the user had set.
Prior to Windows 10, updates were nothing other than patches. Some service packs actually *did* change user settings, and OS upgrades definitely did. The difference now is that we get an OS upgrade every 6 months instead of every 5 years. The patches that are released every month as previously do not change user settings.
Re: Changes on a whim, surprise surprise (Score:2)
In the internet browser subject, yes, but not in all subjects: generally, I don't understand the anti-Google speeches here: it's an USA thing?
Re: (Score:2)
I don't understand the anti-Google speeches here: it's an USA thing?
I don't know.. have they been fucking with you yet? If not, maybe you just havent noticed, yet.
Re: Changes on a whim, surprise surprise (Score:1)
Re: Changes on a whim, surprise surprise (Score:2)
you wake up with bad bugs ...is more like it
New feature in Windows eh? (Score:1)
Re: (Score:1)
Re: New feature in Windows eh? (Score:2)
Just relaunch (Score:2)
If it operates like most of their experiments, they have assigned a random chance to who gets to try to the new feature, and it is reevaluated on each launch to avoid stuck crashing states. Yeah, Google Chrome is not deterministic.
This is why enterprises used Internet Explorer (Score:2)
Re: (Score:2)
They still do. You get security and bug fixes for (I think) a year, then a new base-ESR version comes out and you move to that. The "normal" users are effectively acting as beta-testers.
Re: (Score:2)
I think it's time Chrome offered an ESR version too that doesn't offer random experiments.
Yeah, I know, because it's too much to expect half-competent sysadmins to replace the standard Chrome shortcut with one that runs chrome.exe --no-experiments. Sheesh.
Re: (Score:3)
Two can play this game.
Re: (Score:2)
I would expect a half competent sysadmin to read the documentation.
https://support.google.com/chr... [google.com] doesn't mention Google experimenting.
The referenced policy list at http://www.chromium.org/admini... [chromium.org] doesn't either.
So yes, it is too much to expect half-competent syadmins to set a flag that no fucker knew existed and wouldn't even have gone looking for because what sort of cunt releases a browser with automatic 'fuck you senseless' opt-ins?
People wonder why Chrome isn't my default browser...
Re: (Score:2)
Yeah, I suspect that Microsoft's PR team is salivating over this incident and will be directly or at least indirectly cited when selling Edge-Chromium to enterprise users next year.
"So you get all of the compatibility of Chrome, but we have absolutely zero spyware, your support contracts entitle you to immediate support and all updates will be run through Windows Update. Don't worry we have IE mode built-in so you can even use it for your old web apps."
The first thing that needs to be fixed though is all of
Re: (Score:2)
Here I thought you were ignorant. I didn't realise you were dumb too.
Re: (Score:2)
Re: I refuse job offers from Windows/Chrome users. (Score:1)
Re: (Score:1)
Re: I refuse job offers from Windows/Chrome users (Score:1)
Another case of Google copying Microsoft (Score:2)
And those always end well (not)
Google messed up big time here.
Chrome is a resource hog at the best of times. Time to send it to the trashcan (where it should have been put a long time ago)
Well the underlying feature makes sense at least (Score:2)
It always annoyed me that chrome will continue to render a GIF or otherwise drain my battery when the entire window is occluded. That behavior should have never existed.
So the silver lining on this shit-cloud is that, once they iron out the bugs, that will be hopefully be better.
A browser should not try to outsmart the OS (Score:1)
Good! (Score:1)
"A Google Chrome experiment has gone horribly wrong "
You never learn as much as rapidly as when an experiment goes horribly wrong.
Then at least the right people are looking at the problem.
Re: Good! (Score:2)
FTP (Score:2)
Just on Windows TS? (Score:1)
Sys admins at fault (Score:2)
If your system relies on an evergreen browser for which you have no control over releases, then your system admins are not worth the money you pay them.
Trust us.. (Score:2)
" We want all of your data in the cloud and to lock you up tight because we are Trustworthy(TM). We wouldn't dare think of playing Chernobyl when you least expect it. Honest (old offensive word for Native American)!"
We test in the production environment (Score:2)
LoB