When I clink on links in Mail, opens blank Chrome page

A recent update to anyone not following the Chromium thread, Chromium team is currently choosing not to implement a fix because the design is too risky. They are waiting for Apple to fix this at the OS level, at how the data (the URL) is passed into the application while an update is pending. Realistically, this probably means you won't see a fix for several more months, unfortunately.

Again, the workaround is to restart Chrome to let the autoupdate apply, and then it will work for as long there isn't an automatic update pending. Once it reaches this state again, the issue will be exhibited again.

If you update Chrome, this issue should be resolved. I just upgraded to Chrome 62.0.3202.75 and it's working again.

It is not specific to a version of Google Chrome.
Chrome is waiting to be relaunched because of an update.
Just go to About Chrome page and do an update or relaunch which ever it shows to do.

This recently started to happen on my Macbook w/High Sierra 10.13.1.

I saw the post regarding the fix - restart and hold down 4 keys but that wasn't necessary for me.

I needed to update my Google Chrome. Once the update was complete, problem solved.

The temporary fix is just quitting Chrome, and then relaunching it. This is why updating Chrome, zapping your PRAM, reloading chrome, etc all seem to work, because they all cause the browser to quit and relaunch. Do not yet know the cause, but to get working again you just need to quit the browser.

While an nvram reset seems a bit illogical troubleshooting step - I can confirm this solved for me as well. Running 10.13.2 High Sierra and Chrome 64.x that is up to date. Command + Option + P + R on boot at 2-3 times.

I had the same problem. Speaking with Airmail tech support, they had me switch my default browser to Safari in Mac preferences. I did that, and the links worked. Only, I didn't want Safari to be my default browser. So, I switched it back to Chrome, and like magic the links were opening correctly within Airmail again.

The issue lies in Chrome itself. Any links clicked open a brand new window with just the 'new tab' page open, regardless of where the link came from (emails,webpage etc..)

in chrome, go to: chrome://restart

that will fix the issue.

Fixed this issue by acessing "About Google Chrome" and clicking on the "relaunch" button on the right side of pending update.

All I had to do was reboot (without zapping the P-RAM). FWIW I had a *lot* of Chrome tabs open and hadn't rebooted in several days. But just shutting down and restarting the Mac did the trick.

If this still happens with latest version of Chrome, quit the browser completely (hold cmd + Q) and reopen. It fixed this issue for me every time.

Hi Douglas,

As stated in my six earlier replies, this is a known issue and there is no permanent fix. The current workaround is to relaunch Chrome, thereby applying the update that had been pending.

Some new, canonical information:

The Chromium team has identified and acknowledged this bug in High Sierra.

The underlying issue is that after Chrome finishes a silent background autoupdate (but before it has been relaunched to install the update), links are no longer being passed to the correct version of the running browser. It's been especially hard to track this down because relaunching the browser would fix the issue since that would launch the new, updated version.

There is currently no known workaround besides restarting the browser to apply the pending update. Resetting PRAM and any other catch-all maintenance fix is not a direct solution, and the only reason it works is simply because the newer version of Chrome is now where the link is being routed to. The issue will absolutely reoccur as soon as Chrome has a pending autoupdate that has not installed.

They have it as a Priority level 1, so hopefully we see a fix for this on the stable channel soon. Here is the issue in the Issue Tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=777863

I had the same issue, I have updated Chrome and this problem has been solved now, I have version 63.0.3239.18

So it seems that it really was a Google problem.

I updated Chrome and relaunched and it fixed it