I have been playing around with the PIA desktop client and all kinds of VPN settings today, so it's not out of question that something I did screwed something else up, but whatever happened, whenever I now go to pandora.com it automatically directs me to privateinternetaccess.com.
I have restarted chrome, my PC, re-installed chrome, removed the PIA desktop client, removed the tunnelbear desktop client and chrome extension I still had installed and disabled all my other chrome extensions.
Accessing pandora.com through Edge or Chrome's incognito mode works fine.
Visiting http://www.pandora.com/restricted (Which is where I should land when visiting pandora.com, since I'm in Germany and currently w/o a VPN) actually loads the expected page from Pandora. So it's not like the entire domain is bricked.
Kinda out of ideas over here.
The thing I hadn't tried was just resetting Chrome, since I kinda forgot I can disconnect my Google Account first to not lose all my settings.
So yeah disconnecting google account -> resetting chrome -> reinstalling chrome(cause why not) fixed the issue.
Related
General Problem
We've had a long-standing problem with our two ExtJS 5.1.0 apps that div scrollbars don't show in Chrome, using only our QA testers' AWS Workspace Chrome browsers. They don't see this in other websites using that Chrome, only our two applications. We've been able to ignore this since the problem was isolated, but now a user is having the same problem.
We've been able to confirm that the difference is that wherever there's a div that should be overflow: auto is being generated as overflow: hidden. So scrollbars for grids, dropdowns, etc don't render but the div can still be scrolled via other means (tabbing, page down).
I've been looking for general ideas about what could cause this--is it ExtJS? Windows setting? Chrome setting? Again, the problem is isolated to AWS Workspace's Chrome and a user's Chrome.
Versions
Chrome:
AWS Workspace has exact same Chrome version as me, 79.0.3945.88.
User has Chrome 80.0.3987.149 (up-to-date).
Windows:
AWS Workspace is Windows Server 2016 Datacenter.
User has Windows 10.
What We've Tried
These are all troubleshooting steps we've tried in the AWS Workspace Chrome:
Disabled all extensions. Also ran in incognito mode which should do this also. The extensions are nothing that I don't also have, and I don't see the problem.
Inspected Chrome's flags--they're all default, and again not different than what I have.
Disabled Chrome's “Use hardware acceleration when available” setting and restarted Chrome.
Previously opened a ticket up with AWS and they were unable to help.
Researched any connection of this to Chrome, ExtJS, or Windows Server 2016 Datacenter without luck. Only found general information about "what to do if you have scrolling problems in Chrome".
Other Problems Our Apps Have in AWS Workspace Chrome
Listing these in case it helps trigger any ideas about the underlying problem, but focusing on the scrolling for now. Again these are isolated to Chrome in AWS Workspace (unclear if the user is seeing these also):
Drag and drop doesn't work.
Tabs that aren't the selected tab when the tab bar is loaded don't load at all.
It turns out that the problem was related to touchscreens. Our user has a touchscreen laptop (and didn't realize it for a while, we asked about this early on). And the Amazon Workspaces are touchscreen-compatible, as they have a "HID compliant touch screen" device listed in Device Manager > Human Interface Devices. So something about touchscreens + Chrome/Edge is telling ExtJS 5.1.0 that the device is mobile and scrollbars shouldn't be rendered.
Solutions:
For our user, she was happy to disable her touchscreen device and this worked for her.
For Amazon Workspaces, disabling the touchscreen device did not work. For Chrome we were able to resolve by adding --touch-events=enabled to the Chrome shortcut. There are various touch-related Chrome flags mentioned online as a solution, but none of those are available in the current version. Anything touch-related we did find in Chrome's list of flags didn't help.
I haven't looked for a solution for Edge if someone uses Edge and wants to keep their touchscreen. This is fine for us right now. (Because we realized Edge has the problem also, presumably due to Chromium. Did not see it with Firefox.)
And I did confirm using ExtJs' Kitchen Sink examples that I can replicate the problem in 5.1.0 with both a touchscreen laptop and an Amazon Workspace. Also that I can't replicate the problem in the current version, so we should be good once we upgrade.
I am running Node.js on localhost:3001 and unintentionally wrote some code with an infinite while loop. This locked up Chrome to the point where the only resolution was to kill the browser. Since then, I found the problem in my code using Firefox, and fixed the code, but even after restarting Chrome, it will not load my page. I even changed the port that the server runs on, and the cache is disabled with developer tools open - Chrome simply refuses to load the page. I see a single request to the server for the page, but in Chrome it just registers as Pending.
Has Chrome maybe flagged this page as suspect, somehow? How do I get it to play again? I would at least expect Chrome to offer some opportunity to kill a tight loop - like Firefox does - but I've yet to see it. Is there some setting I can tweak? I'm on version 74.0.3729.169 (Official Build) (64-bit), although now that I opened the About page, I see that it is updating Chrome, so maybe that will fix it.
UPDATE: It didn't fix it, but it works in Incognito mode. ???!!!
UPDATE: Disabling all of my extensions also didn't fix it!
I found a setting in Chrome: "Continue to run background apps when Chrome is closed"
I turned that off, and now it works again.
Our application uses a popup window to show a report. This works in every browser except Chrome.
In Chrome the URL in the Network tab of the inspector has a blank response. I also see Chrome loading an inject.preload.js script from disk cache?
This exact same page works in Firefox and Safari as well. I haven't been able to check IE yet (i'm on a mac today).
What is this inject.preload.js script and why would Chrome not load a URL in a popup?
The exact same code running staging servers works, the popup loads just fine. In production it works everywhere except Chrome. Both staging and production use SSL, have the same config, etc.
I unfortunately can't link as its a secured site.
Inject.preload.js is generally some sort of adblocker. It could be the case that its acting up and blocking your popup. If it is the case, it would show as an icon to the right of the address bar.
I am experiencing an issue with opening a Microsoft Office Document, using IT Hit WebDAV AJAX library, in latest Chrome 39.0. running on Windows OS. It is a sporadic issue that occurs only in Chrome, and it happens when one opens a document multiple times. Word instance won't start, the page freezes and browser becomes unresponsive, and Chrome suggests killing the page. The only solution is restarting the browser, which solves the issue.
I have tried opening a document in Chrome on Mac OS X, and it is working fine. So are Mozilla and Safari on all operating systems. It seems to be a Chrome + Windows issue only.
Has anyone experienced this issue and is there a fix?
The Microsoft Office plug-in that opens the document displays a warning popup "Some files can harm your computer.", which is a modeless dialog:
If you quickly click on a link that opens the document more than one time the dialog will hide behind the main web browser window. As a result the web browser window is blocked.
You need to switch to that dialog and confirm or reject document opening, otherwise after some time Chrome will ask you if to kill the page or wait.
Note that there is no way to avoid that dialog, this is a built-in MS Office functionality as far as I know.
Chrome will only work good with ITHitWebDAV if the user has got Office 2013 or superior.
Google is blocking all Java applets and NPAPIs now, so good luck with that. I just detect the browser of the user that wants to edit a document, and if it's chrome, I warn him to change to another browser like Firefox with a modal, and that's all.
Very poor support between Chrome and ITHitWebDAV, and no much you can do about it.
So i have been running into this problem with a lot of Wordpress sites lately, usually occurring when i am logged in as Admin, so i couldn't post here because no one would be able to view the problem. However, i just found a site that it happens on that doesn't require admin creds.
http://www.otisports.com/
When i visit this site in Chrome (Version 34.0.1847.137 m), it just displays a blank page. No errors, just the (what now seems standard) event.returnValue is deprecated. Please use the standard event.preventDefault() instead. warning. I have seen that warning signify problems on the site, but they are usually minor, not to the extent that the above URL displays. However, if i open an Incognito window and visit the site everything works perfectly and there is no warning. Does the Incognito window deal with webpages in a way that is so entirely different that it would cause something like this to happen?
I have been racking my brain trying to figure this out. Can anyone reproduce this? is it a bug in chrome?
EDIT: I just tried to open a bounty on this question and the EXACT same thing happened. In Regular Chrome, nothing happened when i clicked the start a bounty link and i saw various errors Undefined is not a function however in incognito everything worked perfectly. what gives?!
EDIT: Yes, i have cleared the cache, history, cookies, everything, and i still get the same errors. I cant even post a comment on this question because of errors...
I came across the same issue when trying to open evernote.com. It loaded successfully while using incognito mode in chrome. Let me share how I fixed this even though the original post is way too old. But maybe someone can find it useful.
I'm using chrome (Version 73.0.3683.103 (Official Build) (64-bit)) running on Linux Ubuntu 18.04.2 LTS.
I tried disabling all extensions and clearing browser data/cache but nothing worked. PS: Disabling adblock previously worked for me. Yes, I stumbled over the same issue before and whitelisting evernote in adblock solved the issue. But it didn't now.
The following is what worked for me:
Open developers tools (CTRL + SHIFT + J).
Navigate to Applications tab.
Choose Clear storage from the side menu
Hit Clear site data button.
After reading the comments I dug into chrome and saw there was a bunch of extensions still sitting around that were definitely malware and I thought I had previously deleted. Instead of picking through them one-by-one, I just deleted everything, re-installed Chrome, and now everything works great!
I had the same issue. My application was working in Incognito mode and in Firefox but not in Regular Chrome. I even disabled all the extensions but no luck. I eventually cleared the Cached images and files because on developer console I found out that the regular chrome was still picking up the old file due to caching. So as soon as I cleared it, my app showed up like a rocket :)
Try removing any non required extension .
Specifically AdBlock
I resolved the problem post that.
Since on Incognito , extensions are disabled, hence page run as expected.
I resolved this unforeseen issue using following steps.
CTRL + SHIFT + DEL > Clear Browsing Data.
Cookies and other site data
Cached images and files
This is for Chrome Browser.
Open Console (Ctl+Shift+I) first.
Then under the application tab, you will find some options on the left, find out the application there, you will find it at the top.
There you will find Service Workers.
Under Service Workers, there will be three checkboxes. Select Update on reload checkbox and reload again.
I had the same issue after installing React-Sight Extention.
The Page hanged but not in the incognito mode.
Try deleting any recently added or junk extension.
Delete your cache.
That worked for me
I had a similar issue in chrome, in my case the problem was that I could log in to my university library's website only in incognito mode. After some digging, I figured out that Google Translate extension was set to automatically translate any page. When I turned that off and instead selected never translate that specific page, it started working in the usual mode as well.
This is rather an old issue but still happens. None of the solutions recommended here and there did not solve the issue in my case.
I somehow noticed this is related with a -some kind of- corruption on the user profile.
This is how I solved it:
Close all Chrome browsers.
Open a Google page on Chrome.
Sign-out from Google (rigt click your profile picture on a Google page, not on the Chrome itself), and sign-in.
If this doesn't work:
Close all Chrome browsers.
Right click Chrome icon and select Google Chrome.
Delete your Google profile on the "select your profile" page.
Close Chrome.
Open Chrome, sign-in.
uBlock Origin was the culprit in my case. Once I allowed the site in uBlock Origin, pages loaded correctly in normal Chrome.