setPosition (many, many times) on a marker using gmap-v3 makes Google Chrome crash.

[Jens Lykke Brandt]

Hi there,

Example: http://ingenadgang.dk/chrome/test.htm

It works in all other browsers - not in Google Chrome (12.0.742.100 and 14.0.794.0 (Canary)): Here the Marker moves for about two minutes or so - then Chrome crashes ("Aw, snap").

I've posted the issue at the chrome-bugtracker as well: http://code.google.com/p/chromium/issues/detail?id=86520

It's a setPosition many, many times on a marker.

The memory-usage builds up, is cut down once and then it builds up again until it crashes.

Code snippet:

...

        --- SOME STANDARD INIT CODE ---

        // Start interval

        setInterval("setpoint()", 40);

    }

    // move point

    function setpoint() {

        // Set new position

        marker.setPosition(new google.maps.LatLng(lat, lng));

        // Update position

        lat += 0.0000001;

        lng += 0.0000001;

    }

...

Ideas?

Kind regards

Jens

[Chris Broadfoot]

I can't reproduce this. I actually left it on overnight and it's still going.

--

http://twitter.com/broady

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/9CxlfTr40ToJ.
To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Ed Estes]

I tried it and got the error as well.  (might have been more like 5 minutes - I wasn't counting)  I was dragging the window/map to find the marker since it had walked off the visible screen.  (don't know if it was related)

I will play with it more to see if I can reproduce on a more consistent basis.  Let me know if there's any specific testing you want me to try.

--Ed