Brichter says the web browser installs the auto-update. My guess is that there is some fallback logic in MacOS where it uses a public DNS server after the local DNS server fails to respond.Īll I had to do is set DNS servers to Google's Public DNS IP addresses. Chrome is Bad is the title of a website released by developer Loran Brichter that claims Google Chrome is slowing down Apple Mac computers. I don't know why the Internet even worked at all.
It turned out that my Mac had the DNS server set to a non-existent local IP address, something like 10.0.0.1. But overall the internet was working just fine and no other device, including my work MacBook, had that problem. On Android, open the Chrome apps settings, tap Privacy and Security, then tap Preload pages and select Standard preloading. Using tools like brew and pip was a nightmare as it took forever before they started downloads. Chrome would show “Resolving host…” for a few seconds before loading websites and it was exasperating.
My new shiny MacBook Pro had an issue with resolving host names. If you still feel like Google Chrome is slowing down your Mac performance, by all means, go ahead and remove it, I recommend Safari instead. How to fix Chrome "Resolving host" issue on Mac
0 kommentar(er)
