Google’s confidential Chrome experiment crashes thousands of browsers

Google left tens of thousands of machines in companies using Chrome browsers that were broken after having a shift that was experimental. Business users obtaining Chrome stored blocking access, seeing displays on Chrome tabs and rendering it completely unresponsive.

It left many IT admins confused over the issue, as companies control and manage upgrades.

Following complaints, Google has been forced to show it had started an”experimentation” on stable variants of Chrome which had altered the browser’s behaviour. The experiment was created without users or admins warned about the changes in Google. Google had just flipped the switch on a flag to allow a fresh WebContents Occlusion quality that’s intended to suspend Chrome tabs once you transfer other programs on top of these and reduce resource use once the browser is not being used.

“The experimentation/flag was around in beta for 5 weeks,” explained David Bienvenu, an applications engineer at Google, at a Chromium bug thread. “It had been turned on for steady (e.g., m77, m78) through an experiment which has been pushed to published Chrome Tuesday morning.

Prior to this, it was around for approximately 1 percent of M77 and M78 users to get a month with no reports of problems, sadly.”

Google rolled the change back night, after reports from companies with thousands of users. “I will rollback the launching of the experiment and attempt to work out how to cope with Citrix,” mentioned Bienvenu from the bug thread.

“It has had a massive effect for many of our Call Center representatives and not being able to talk to our associates,” described a Costco IT admin at the Chromium thread. “We spent the past day and a half trying to figure out this ”

One IT admin which alerted The Verge into the issue stated “we believed that this really is a shady thing which Google can upgrade Chrome softly without declaring anything and can affect 100,000+ people on a whim.” Those concerns are represented by countless answers on Google’s service forum, the bug tracker thread, and on Twitter and Reddit.

It’s left IT admins mad that they have wasted resources on trying to correct problems in their surroundings and time, and queries over why Google chose to make a shift. “I’m stunned by your answer,” said one IT admin in reaction to Bienvenu’s affirmation on the difficulties. “Can you find the effect you made for thousands of people with no warning or explanation? We’re not your evaluation subjects. We’re running services for multi million dollar applications.”

We have achieved for comment about the Chrome problems to Google, and we’ll update you.

Leave a Comment