Cannot open any pages, including internal chrome:// pages
Reported by
lok...@gmail.com,
Dec 12 2017
|
||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:57.0) Gecko/20100101 Firefox/57.0
Steps to reproduce the problem:
1. Launch Chrome
2. Attempt to navigate to any page, including chrome:// internal pages
3. Page hangs indefinitely until the "this page is taking too long" notification pops up
What is the expected behavior?
Pages should load - especially internal, non-network require pages like chrome://settings.
What went wrong?
Other browsers tested:
Firefox 57.0.2
Safari 10.1.2 (10603.3.8)
After a reboot of my Mac, I attempted to relaunch Chrome and bring back all of my tabs - every tab hung, and I saw no traffic on the network. After another attempt, I had the same issue.
I then stopped Chrome and moved "~/Library/Application Support/Google/Chrome" to "~/OldChrome", relaunched Chrome, and the same issue happened.
Did this work before? N/A
Chrome version: 63.0.3239.84 Channel: n/a
OS Version: OS X 10.10
Flash Version: Shockwave Flash 21.0 r0
,
Dec 12 2017
Just attempted to try Chromium 65.0.3292.0 with homebrew and it failed in a similar way.
,
Dec 12 2017
,
Dec 12 2017
Issue 794006 has been merged into this issue.
,
Dec 12 2017
Rechecked this issue on Mac 10.12.6 using chrome version 63.0.3239.84 and unable to reproduce it. Able to navigate to any web pages including goole internal pages. @ loki77 - Request you to please disable any third-party extensions if installed, restart machine, relaunch chrome and try again. Please update us with your observations. @pbommana: Request you to please try on a Mac 10.10 machine as inhouse do not have this version of Mac OS. Thanks.!
,
Dec 12 2017
I rebooted once more last night and attempted and it still had this issue, but after going home from work and rebooting one more time it cleared up. Not sure what could have caused this - I had disabled everything (by moving my Chrome settings/extensions/etc directory out of place) when testing it before and nothing seemed to help. Now at work again, it seems to work/launch fine, so not sure what it was. Thanks for all your help, and sorry for the false report.
,
Dec 12 2017
Thank you loki77@, based on above comment marking the bug as wontfix. |
||||
►
Sign in to add a comment |
||||
Comment 1 by lok...@gmail.com
, Dec 12 2017