I have thought that that requiring the creation of new LatLng objects could cause an issue - however I have implemented my own solution (not using GPolygons) in V2 that constantly creates new LatLng objects and does not suffer from leaks.
I'm sort of restarting my approach from scratch with V3 - looking at what the API provides and hoping that there is a simple way to do this. -- 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.
