On Apr 8, 11:03 am, Andrew Leach <[email protected]> wrote: > On Apr 8, 10:41 am, CharlesHarrison <[email protected]> > wrote: > > No, Mike's right. It's not the map which stops working, it's the > browser.
I'm not entirely convinced: 1) The behaviour is browser independent 2) The browser shows no sign of stress such as maxing the CPU 3) Everything appears entirely normal, all the normal status bar messages about communicating with Google servers appear as usual 4) But the map is blank 5) Sometimes changing to a radically different zoom level will cause it to start working again 6) Thereupon returning to the zoom-level previously set shows the map *instantly*, suggesting that the tiles were there all the time, but weren't drawn on the map when they should have been This all reads to me like a systematic error in Google's coding in not being able to keep up with the call backs in some way, so the map loses track of what it's doing. The effect of having a second map exacerbates the problem, because by hogging the bandwidth it introduces a greater time lapse between tiles being requested and their being received for placing on the map. > > Hence I need to know if there's an 'official' way to clean up and > > relaunch the map. > > There isn't. If you simply create a new map in your div you run the > risk of memory leaks. That was what was worrying me. Nevertheless as my hack of setting the map object to null seems to actually work, I'll leave it in place until anyone can suggest something better. There is already a note on the page suggesting how to avoid the problem in the first place. -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
