Those things are the hardest to fix.And the fix is the important part. It is a real thing, but it's one of those things that just isn't happening to everyone. But I'll bet that other people who work here and use a Mac have seen it. While Mac users have had some complaints about Chrome (again, something Google and Apple need to work out), not every user for the past five years has had their MacBooks stop responding because they have Chrome installed.The worst part of this bug is that not everyone sees it.I got with a few other writers for Android Central who have an Apple computer here in our morning meeting, and we've never seen this exact behavior, even when Chrome was eating all the RAM or making the fans spin like helicopter blades.
Is Google Chrome Bad Update Mechanism WorksI hope you can track it down and give us an honest postmortem.While Britcher is insinuating that it isn't broken because Google somehow wants to hide things (Keystone isn't hidden from view, but the macOS application tracker doesn't show it unless it is running), there is another reason — the Chrome auto-update mechanism works just fine on every computer that's not a Mac. Why would auto-update software need to take up a massive portion of CPU on a ton's of people's computers, all while hiding itself?To all the good people at Google who work on Chrome: something is going on between the code you're writing and what is happening on people's computers. As Loren Britcher puts it on his Chromeisbad site:The fact that it hasn't been "fixed" in 11 years might mean that it's not actually broken. But don't expect a fix anytime soon.Keystone has been in Chrome for macOS for a long time and through many different versions of the OS. It even works fine on Linux if you install the package from Google instead of installing Chromium.Here's my best guess about what's happening, and it's only a guess. It works fine on the most basic and the best Chromebooks.![]() ![]() Google might look to market share and decide that it's still best to spend almost all resources on obscure Windows compatibility bugs since Windows has a whole lot more Chrome users than macOS does, and Google only cares about profits. Apple will just tell you to use Safari and not care any further because Apple only cares about profits. Since we know that neither Google nor Apple ever stops updating things, there's a good chance, this is the problem.The bad news is thinking about the priority of finding a fix by both companies. We haven't, and most people who have actually used one think an Apple computer is pretty damn good. If you see it, you should file a bug report.If it's not a case of incompatibility, then we all would have heard for years how Macs randomly freeze and grind away every once in a while for no reason, and it's so bad you shouldn't buy one. That means one of the two things — an updated WindowServer or an updated Chrome auto-updater — isn't compatible with the other.Something has changed in either macOS or Chrome's update utility that is causing all of this. Remove mac ad cleaner adwareAll we can hope is that it comes soonish, so the people affected by the issue aren't left hanging out to dry for too long.
0 Comments
Leave a Reply. |
AuthorDoug ArchivesCategories |