I'm not sure why I have this error. Everything seems to be running fine and I don't have the error in Safari but when I open Chrome, it seems to not be happy.
Some context; I am running node and doing some single page d3 dabblings. I'm not developing any chrome extensions so I'm confused where this is coming from.
Similar but didn't help SO post
Related
Would like to share this issue I recently debugged.
I was getting this error in Chrome console for a particular page.
Debugged the script - No error, actually the script is working correctly in some other modules and components.
"officeUtilities" script is not loading due to this error.
Although I couldn't fix it in the active session of browser, following worked for me.
- Opening page in Chrome incognito mode and other browsers (Firefox, Edge, IE).
I think it is caching issue. I deleted all browser cached images and files , but that didn't work. I didn't tried to delete all history, that will end up logging out of multiple sites.
Since I found a alternative way to test the page, I'm Okay with it.
I am running a Flask web app on localhost, for development. I do a Ctrl+F5 (after I have made a change to JS or CSS). Once in 3-4 such instances I get ERR_CONNECTION_RESET errors in the Chrome console, for SOME of the external JS/CSS (Bootstrap, Jquery etc) that I am fetching from CDNs. But there's no pattern to it. I am getting this from MaxCDN, cdnjs.cloudflare.com, and code.jquery.com, but not all at once.
Some of these errors are:
GET https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css net::ERR_CONNECTION_RESET
GET https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2 net::ERR_CONNECTION_RESET
GET https://code.jquery.com/ui/1.12.1/jquery-ui.js net::ERR_CONNECTION_RESET
I am getting similar issues in Firefox:
Loading failed for the <script> with source “https://cdnjs.cloudflare.com/ajax/libs/jquery/3.1.1/jquery.min.js”.
This is happening only on my laptop. On another laptop, running the same code on that laptop's localhost, and accessed and hard refreshed through that laptop's browser works fine.
This issue started occurring only recently after I reinstalled Windows on my laptop.
I looked at some of the other questions on SO such as this, but that didn't help.
I'm using SwaggerUI over a Servicestack v4.07(licensed) application to expose REST specs.
Everything works on Firefox and Chrome, but when i try to open the swagger index with IE9 or below, it crashes, showing nothing but the page header, so no service is listed.
Actually i can reproduce this but even on the swagger demo website http://petstore.swagger.wordnik.com/
When i open it with IE9 it crashes because of a (probably) known issue: https://github.com/wordnik/swagger-ui/pull/204.
When i open it with IE8 instead the fiddler tells me that there's no such defineProperties method for the Object class(exception raised from shred.bundle.js)
Does someone know about such issues?
I am getting cross-domain request errors in chrome, when I try to perform a hit test with EaselJS (which uses getImageData()).
Unable to get image data from canvas because the canvas has been
tainted by cross-origin data.
The weird thing is that I'm running a local server and all images are served from this localhost:3000 and render nicely.
How do I use Chrome's Dev Tools to figure out the issue? All my images, html and JS are grouped under :3000/ in the Resources tab. What's the next thing you would check?
There might be something else in your code setting it off. Pour over everything for other examples.
Alternatively, install Firefox and put on Strict errors/warnings. I use Chrome as my main browser but sometimes FF has much more verbose errors/warnings that can make debugging a complex issue easier.
Also for the record, if you launch Chrome with the flag --allow-file-access-from-files it won't throw any of these exceptions.
Using the example chat application here, I've written a simple Socket.IO application served over Node.Js which polls a JSON file using a fileRead from the server side and broadcasts the parsed JSON values over to the client side, where I've displaying them.
This works really well in Chrome, Safari and Opera (all those who support WebSockets).
However in Firefox, it fails until I start the Firebug console. That's when the handshake happens and the data is displayed.
In IE, it just doesn't work.
When I deploy the same code with SSL, it works everywhere. Any ideas on what I'm doing wrong here? EDIT: Now it doesn't seem to work on SSL too :(
However in Firefox, it fails until I
start the Firebug console. That's when
the handshake happens and the data is
displayed.
Sounds like this might be a console.log() problem. Firefox will hang if you call console.log() without actually having a console open.