Refreshing any page with Google Maps API crashes IE8 - google-maps

For the past couple of days we've been experiencing problems with web pages using Google Maps API V3.
Originally I thought it was one particular page on our website, and have spent at least a day trying to find the cause.
This morning I found it was any page with a map on our website, and have just found it's any page on any website with a map.
We are using IE8 on Windows XP, the problem is that on a page with a map is refreshed IE8 crashes.
If "Enable automatic crash recovery" is on in Internet Options/Advanced then you'll get a "balloon" error:
This tab has been recovered
A problem with this webpage cause Internet Explorer to close and reopen the tab.
If "Enable automatic crash recovery" is off, the usual "Internet Explorer has encountered a problem and needs to close" message box appears, but clicking Debug just closes IE.
This happens on the simple example page from Google, it will load fine, press F5 and IE will crash.
https://developers.google.com/maps/documentation/javascript/examples/full/map-simple
This only happens on IE8 on Windows XP. IE7 on XP and IE9 on Windows 7 are fine, as are Firefox and Chrome.
Can anyone else confirm this, and have any idea how to resolve?
Thanks,
Mike
Update:
Have found that it works fine if XP is started in Safe mode with Networking

Related

Webpage made using Polymer terminates on Google Chrome

I have made a webpage using Polymer. The webpage doesn't open on Google Chrome (both Windows and Android). When I try to open the page, Chrome shows "He's Dead, Jim!" message on Windows and "Aw, Snap!" message on Android. I have reset the settings and reinstalled Chrome but the problem still continues. Can anyone tell me how to solve this problem or the reason behind it?
https://www.googledrive.com/host/0B2Zii8voDW6QcGduNnl1cFBReXc/fold/
maybe you can check if there is any error in your page, which stop polymer initialization:
https://www.polymer-project.org/docs/polymer/debugging.html#unregistered-element-bookmarklet
Btw, did you try the official demo page with your browsers? If they work, then it's your code problem.

IT Hit WebDAV AJAX Library on Chrome becomes unresponsive

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.

Chrome developer tools: constant "page unresponsive" messages

When I open a separate Chrome developer tools window in order to look at a page's JavaScript code I get this window in regular intervals:
When I click "wait" the window goes away but comes back soon after.
How can I get rid of this annoying message?
This happens on Chrome 32 on Windows, and on different websites (e.g. http://spiegel.de).
it does seem that the issue is with the 32.0.1700.102 version of Google Chrome.
I've got several users who are experiencing the problem. It only seems to happen when you are working with sites that open popups (the kind you want) such as opening and email in a new window in Google Mail.
Its seams like the latest update may have helped fix the issue(32.0.1700.102 m), or some users are reporting that the v33 beta does not have the issue. https://productforums.google.com/forum/#!msg/chrome/1PgURxP9_-k/It9TupoPEgQJ
Bug report here:
https://code.google.com/p/chromium/issues/detail?id=335248

"Aw Snap" mesasge in Chrome when using Silverlight

I'm getting the "Aw Snap" message consistently in Chrome when performing the following:
Load a page that displays a silverlight rendering
Click on a button that fires off a fancybox containing an iFrame that contains the same Silverlight rendering
Close the fancybox
Receive the dreaded "Aw Snap" message
Reload page and page loads up again
Notes:
This does not happen in IE
This does not happen in Firefox
When I go to chrome://crashes/ there is no record of the crash
Chrome Version: 24.0.1312.57
Silverlight Version: Silverlight 5 (5.1.10411.0)
Searching through Google's Chrome issue board yielded very little and any issue reported that was similar was either years old or did not have a response. Hoping that someone has encountered the same problem and has a workaround.

Google Analytics not loading in Chrome

When I try log in to Google Analytics in Chrome, the page doesn't load. Very odd. I just get what you see here:
I've never experienced it before recently, and it works on the same computer with Safari, but for about a week now it hasn't worked on Chrome. Any advice would be appreciated.
Likely an ad blocking plugin that had its ad database updated.
I know this question is old but I thought I'd add my answer.
For me it was adblocker on chrome. Click the hand in the red octagon next to your address bar. Go to options and click "show adds on web or domain", add the the domain https://www.google.com/analytics/ and that should fix it.
Clear your cache and disable any plugins that might be interfering.
Try in incognito or in private browsing as it will stop interference from extensions especially adblocking extensions
I tried on Incognito mode and different browsers but it is still not working. I also tried this on Chrome: Settings > Reset > Restore settings to their original defaults. I am still experiencing the same issue reported in this question. When I gave up trying everything on Windows, I tried from an iPhone (not the app, but visiting Google Analytics from a web browser on my iPhone 7 Plus in Chrome, no success. Then I moved to OS X Yosemite Version 10.10.5, and still the same, Google Analytics was not working. After spending several minutes trying, maybe for about an hour or more without success, it suddenly started working everywhere.
My conclusion is that most likely this was a bug in Google Analytics. I should have tested my Internet speed to see if the cause was poor Internet speed, but other pages were loading correctly. So I assume it was simply some kind of bug in Google Analytics.
EDIT: Today I am experiencing the same problem, and this is about 24 hours after the answer above that I posted yesterday. I went to http://www.speedtest.net/ to test my Internet speed, and these are the results:
Ping: 6ms
Download: 2.68 Mbps
Upload: 5.17 Mbps
Then I saw a pop-up telling me that an internal error had happened, and please close and open again the browser. This was definitely a bug in Google Analytics' service.
This is what I was seeing today, with Google Analytics never loading:
My problem was that google analytics wasn't collecting data from some users using browsers like Chrome and Firefox, and also when the users were active on my website, google's Real Time Reporting didn't work.
I found out that the users were using browser plugins like: AdBlock or disconnect.me wich were blocking the data collection.
I hope this helps someone because google brought me here while I was searching the internet for a solution to my problem.
And with some bits from here and some bits from there I managed to figure out what my problem was.
Thanks.
I had the same problem (Chrome, OSX), but I found out it had something to do with my extensions, as Google Analytics would properly load in Incognito Mode. In my case the extension Windscribe - Free VPN and Ad Blocker were preventing Analytics to load. I fixed it by whitelisting the domain.