On Sun, Feb 7, 2010 at 12:45 PM, bratliff <[email protected]> wrote:
> On Feb 7, 12:09 am, Ben Appleton <[email protected]> wrote: > > IE6/7 have a slow garbage collector. Once every 256 object allocations > IE6 > > will traverse the entire working set of allocated objects. This can hang > > the browser while the mouse is moving. IE7 runs the GC every 1024 > > allocations and even then the browser hangs. These 2 browsers are > throttled > > at 20 and 50 frames per second. Other browsers are not throttled. > > Thanks Ben. Glad to know you will not have to throttle Firefox. If > you have to shackle Internet Explorer, fine with me. I rarely use it > except for compatability testing. > > You cannot prevent the "mousemove" event from occurring but you can > absorb it in the API without passing it to the application. I do not > see how it influences garbage collection. Passing the event to the > application ought to be a simple function call. Perhaps the LatLng > object is causing the memory consumption not the event itself. That's right - forwarding the event is fine, but it can be slow to provide listeners with an event Object including a Point and LatLng. We considered reusing Objects between calls, but that prevents the listener from storing the Point/LatLng. -- > 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]<google-maps-js-api-v3%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- 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.
