I can confirm this too. I'm seeing a memory leak even though I'm refreshing the iFrame in which my map is stored, so I would expect all objects to be destroyed during the reload.
I'm fairly certain this does not happen in Firefox. I built a map that refreshes every 60 seconds and tested it with Firefox for hours without failure. Is there a problem with IE and garbage collection? On Jul 28, 7:03 am, Ela <[email protected]> wrote: > Hi, > I'm in a team which is actually programming a business application and > we want to use google maps as the map component. > The problem I have for a while now is that all examples I find within > the documentation causememoryleaks in IE. > I'm using IE8 on Windows 7. > Our cusomers also use IE 7 and 8, so there is no way to tell them to > use another browser, if the browser might be the reason (I don't think > so). > > For examle, take the Hello World example from > herehttp://code.google.com/intl/de/apis/maps/documentation/javascript/tut..., > this is a very simple page. But if you load the page in IE and press > F5 multiple times, you can see that thememoryusage of IE is > constantly growing and growing and IE will never free thismemory. > > This is an absolutly obviousmemoryleak isn't it? > > I've googled through the group and other pages but couldn't find a > solution which unloads EVERYTHING from the page and frees thememory > of google maps' api. Is there any way to do this? > > I'm wondering why so many example code snipplets don't care about > cleaning event listeners or removing objects from arrays and > references etc. Do the google api simply don't care about that? If > this is the case it would be great to know, too!! > > Back to my main problem. The application I'm currently working on is > an ajax application. The user will not reload the page until he logs > out. That means that anymemoryleaks in javascript code causes the > application to unserviceable after some time. > The application uses tabs (jquery). On each tab we have a map with a > lot of markers and other overlays. > The problem is, that if I create a map object for a tab, work with it, > and than close the tab, there is no way to unload the map object. > There are no cross references or events which might cause thememory > leaks, it is simply the map object (I'm absolutly sure about this > because I've build several test page to proof this...) > > A simple test would be to create 10 maps instead of one in the above > sample and than unload them (set them to null or what, remove the div > or click F5). > The result will always be the same ->MemoryLeak in IE7/8 and FF. > > Would be very nice if some can help me! > > Thanks -- 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.
