UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. install an extension that used launchWebAuthflow (e.g. https://chrome.google.com/webstore/detail/simple-gmail-notes/jfjkcbkgjohminidbpendlodpfacgmlm/support?hl=en)
2. login into a gmail account
3. enable the two-step authentication for the gmail account
4. click log-in of the extension
5. login screen of OAuth2 should appear, that allows use of extension

What is the expected behavior?
1. user click agree on the mobile device
2. user get logged into the extension

What went wrong?
The window automatically closed after clicked the extension login link. The error message returned to launchWebAuthFlow is "Authorization page could not be loaded."

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: 

The extension worked fine for most of time, and (I believe) the two-step authentication also worked fine in most cases, as I tried that quite a few times myself.

But the problem was reported quite a number of times from the extension reporting page (https://chrome.google.com/webstore/detail/simple-gmail-notes/jfjkcbkgjohminidbpendlodpfacgmlm/support?hl=en). And I finally reproduced the problem last night in my MacBook. I tried to login 5 times, the first 3 times failed with error "Authorization page could not be loaded". But the last 2 times worked fine, without any change in code.

From what I see in the debugging tool, one thing I noticed is, when the browser hanged in the 3rd time, the OAuth window actually tried to be redirected to 'accounts.youtube.com', which then triggered something that closed the OAuth2 window. But the redirection seems not happened in the last 2 times. I am not sure if that's related, however.

Thanks.