I am getting this error message:
A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.
Script: http://maps.gstatic.com/intl/en_ALL/mapfiles/140g/maps2.api/main.js:110
I noticed this with the gmap-5.x-1.0-rc2 version and it persists with newer versions.
This site has been up for quite a while and the map functionality has been very robust. This problem surfaced a couple of months ago.
This is happening because of changes on the google end of things. I am hoping that there is a fix for this.
Comments
Comment #1
dadderley commentedMore details
This error message is from Firefox 3.5. (mac) - it does load the map.
In Firefox 3.1.0.4 (PC) there is no error message and it loads.
In IE6 it produces an error message but loads very slow.
It runs OK (no error) in Opera (mac and PC)
It runs OK (no error) in Safari
Comment #2
jasonh commentedI noticed the same issues. Google's GMarkerManager was causing the problem. Once I set this back to use the API directly, the performance problems went away.
Hope this helps!
Jason
Comment #3
dadderley commentedThank you jasonh, problem solved.
I should have played with it a bit more before posting an issue. I guess it is good that this problem is documented.
Comment #4
Edgez commentedExactly how it is possible to set back to use the API directly?
What should I change in the code?
Comment #5
bdragon commented@#4: Go to admin/settings/gmap and change the radio button to "No manager (use GMap API directly) " in the "Marker Manager" section.
Comment #6
johnvChanging the marker manager as in #5 resolved my problem too, with a map with 500 node locations.
I was testing the clustermarkers, and would never have guessed to set back to 'basic api' marker.
The script error as in #1 appears on IE8, but not on Chrome.
Comment #7
Patricia_Van_Overstraeten commentedThank you !
I had the same problem