This sounds like it might have exceeded the memory available to IE. I would test your app/map in the different browsers with taskmanager running to get an idea of how you are managing resources. If it turns out that you're clipping IE's memory you could try to run the map in a less intense way (e.g. zoomed in with fewer overlays).
Later this year Internet Explorer 9 is released which will improve speed drastically for this sort of situation. Of course depending on your needs, you may find you're stuck supporting IE8 for many years to come. On Sep 12, 2:43 pm, Joseph Elfelt <[email protected]> wrote: > Google maintains its own cache for KML files. > Clearing the browser cache will not clear this Google cache. > > You can tell your code to ignore the Google Cache and always read the > KML file. > Here's an example of the code I'm using to do this: > > masu.kml_url_on_masu = "http://www.mappingsupport.com/p/kml_demo/ > Howson_Creek_trail.kml"; > mykml = new google.maps.KmlLayer(masu.kml_url_on_masu + '? > dummy=' + (new Date()).getTime()); -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
