Sorry to revive a 5 year old conversation but did you ever resolve this? We also have a reasonably complex mapping application that is leaking memory in IE. The JavaScript heap never appears to increase or decrease substantially (looks like normal garbage collection behaviour) but the system memory used by the IE tab creeps up every refresh.
Users of our application have reported it getting slower and eventually crashing when leaving a tab open for a long time, we haven't found any solutions yet. Finding this thread leads me to think that it's possibly something that started when we upgraded to maps API v3 a few years ago. Thanks for any help... On Friday, 10 December 2010 01:27:23 UTC+11, Canam Group wrote: > > "You can try to set clickable: false and flat: true as Ben suggested here > for a 'sluggishness' problem." > > - In my real application, I need my marker to be clickable. I can remove > the shadow, but that doesn't prevent IE from leaking memory. > > I'll take a look at Fast-marker. > > Thanks! > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-maps-js-api-v3+unsubscr...@googlegroups.com. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. Visit this group at https://groups.google.com/group/google-maps-js-api-v3. For more options, visit https://groups.google.com/d/optout.
