enter image description here
This script is generated by chrome. It runs till it times out the site. Any idea where it is coming from? or what is causing?
Do you have any extensions installed? If you do, that's probably why. Looking at how the page is loading a url from the chrome resource, it's probably a corrupted chrome extension. Try disabling each extension you have one by one, to see which one is causing the problem.
Related
I have some 500 errors on the website that I deployed. They are very random - from browser inspect, I can see some image or javascript are not loaded. When I refresh the website, they sometimes come back. Or they are all good but when I refresh the site, some image or Js are missing. Since they come back sometime, I will think they are not permission or missing file issue. Could be the application pool not behave consistently? What can be the reason? Can someone advise. Thanks in advance!
If they sometimes work, then it's not a permissions problem, assuming that everything is hosted locally. This sounds more like a memory, network timeout, or hardware failure issue to me.
I'm working with Wamp, and i just added a console.log line.
console.log("message);
However, the message isn't being displayed in the console. After a bit of research, i found out that the source code of the page displayed on my browser ISN'T including the console.log line.
It seems like Wamp isn't recognizing the changes in my code all of a sudden.
I tried restarting it but still the same issue. Any ideas ?
This is javascript you are amending. Javascript is cached in the browser, so if you make a javascript change on the server it is sometimes necessary to tell your browser to refresh all its cache's.
You do this by loading the page you want to see and then pressing CTRL+F5 (both together) The browser will reload the page and all its resources, bringing up your amended javascript from the server in the process.
I'm working on a web application that requires a manifest file. There is an issue that causes the chrome browser to hang. This issue only happens in this scenario:
I go to the index.html page and let chrome fetch the manifest files
I update the manifest header manually and refresh the page to force chrome to get it again
Chrome starts getting files but hangs after a while
I thought my issue might be related to manifest but it's funny that if I go to chrome://appcache-internals/ and remove the manifest file from there, the app will be booted without any problem. Is there any differences between these 2 way of forcing chrome to get manifest?
maybe it can give me some hints to find my problem.
By the way, not only that tab but also the developer tools on that tabs hangs, so I won't be able to use it.
Although, AppCache has been criticized a lot and for good reasons, your issue might not be unsolvable. A lot of things can break cached files update by the appcache.
Some of the paths to your files are incorrect, if so, file fetching will hang/break
You did not respect AppCache Conventions for you manifest file. Lots of pointers here
Some other thing has gone awry, then you'll need to do some digging.
So for me, the issue of not fetching all the files might simply be that when you drop the file manually from the tools you force chrome to get it for the first time.
I used to be able to post a link like 'apps.facebook.com/my_app' to my business page creating a post with the og: tags located in my canvas page root. This page had a redirect to the page tab (www.facebook.com/my_page/sk=app_12345678). Everything worked fine.
Since a couple of days this isn't working anymore: It still redirects but no image is included.
Additionally, the URL linter now refuses to lint any 'apps.facebook.com' URLs. Says:
Facebook URLs aren't scrapable by this Debugger. Try your own.
Has anyone else seen this? Is this something new? Is there a workaround?
Well, seems to have been just another temporary Facebook glitch...
Works again!
This ain't no spam, the actual website I'm working on (sorry, it's in Latvian).
The problem here is that there is a tracking script provided by AdForm, which Chrome does not want to load. Firefox loads it smoothly. Have not checked with other browsers though.
Since the script is external, I cannot think of a way to debug it.
Has anyone experienced such a problem with Chrome and how do I fix this?
The script is right before the closing <head> tag.
Update
As Blender has suggested, I've tried removing the async parameter before, but to no avail.
You most likely have the AdBlock extension (or some similar one) installed. If I disable AdBlock the script loads just fine in Google Chrome. With it activated, the script gets blocked.
Update
The AdBlock extension (both the Google Chrome and Firefox versions) uses EasyList, which is a list of adserver domains. Any files loaded from these domains are getting blocked by the extension, and adform.net, the domain your external JS file resides on is on the list (do a CTRL+F for it).