polaristo.blogg.se

1. GOOGLE CHROME FOR MAC KEEPS CRASHING UPDATE
2. GOOGLE CHROME FOR MAC KEEPS CRASHING SOFTWARE
3. GOOGLE CHROME FOR MAC KEEPS CRASHING WINDOWS

GOOGLE CHROME FOR MAC KEEPS CRASHING SOFTWARE

"The question is what is reasonable due diligence and software testing," Thornton-Trump says, "for what is essentially a free, yet vital component of the software ecosystem?" Which is part of the problem, of course: Chrome is an excellent web browser, but do you get what you (didn't) pay for? I spoke to Ian Thornton-Trump, a cyber threat intelligence expert and CompTIA global faculty member who has sympathy for Google, who obviously "did not want to break all the Terminal Services, Remote Desktop and Citrix servers in the land." However, there's no escaping that the size of the Chrome user base demands better responsibility when it comes to such updates.

If issues such as the White Screen of Death leads to delays or workarounds when high-severity zero-day exploits are confirmed for Chrome, then the consequences could be dire.

GOOGLE CHROME FOR MAC KEEPS CRASHING UPDATE

Which is problematical as update pushes, or pulls if you prefer, are essential to maintain the integrity of the browser client from the security perspective.

GOOGLE CHROME FOR MAC KEEPS CRASHING WINDOWS

While we are all pretty used to reading about Windows updates from Microsoft causing security and usability issues, Google Chrome has mostly escaped such bad press, until now. We are already discussing alternative options, none of them are great, but this is untenable." We did not realize this type of event could occur on Chrome unbeknownst to us. ZDNet reports one sysadmin stating: "We spent the better part of yesterday trying to determine if an internal change had occurred in our environment without our knowledge.

The incident has left many business users questioning why Google could push out these kinds of changes to what are often very tightly controlled environments. "I believe it's more of a pull than a push thing," Bienvenu said, "so once the update is live on the Google servers, the next time you launch Chrome, you should get the new config." So everything is good now? On November 14, the WebContent Occlusion experiment was "rolled back," and a new Chrome configuration file pushed out to users. Once the reports started flooding into the support forums, Google started digging into the issue. Has Google fixed the Chrome white screen problem? Google, it seemed, had been testing an "experimental feature" which was then pushed out to the stable release. So when the reason that enterprises around the world were experiencing a "White Screen of Death" that locked up the browser and impacted productivity was confirmed on November 14, it came as something of a shock.

These come with a warning: "Canary can be unstable." Unsurprisingly, nobody using the Google Chrome browser in a "live" business setting, where stability isn't just a nice have but essential, would use such an unstable version of the browser. This did not mean the end of new feature experimentation, though, and developers have been able to test these by way of the nightly Chrome Canary builds. Google announced the closure of Google Labs on July 20, 2011. It was here where new features could be toggled on for testing, with the user acknowledging that it was at their own risk. Many users of Google products such as Gmail and Calendar will remember the Google Labs ideas incubator. Some Google Chrome users have been experiencing a 'White Screen of Death' Getty Images