On Dec 3, 3:41 pm, Canam Group <[email protected]> wrote:
> Hi,
>
> I'm migrating my map application from V2 to V3.
> I'm now done... and everything works fine with Firefox.
>
> I wanted to try with IE, it works well, but it ends up taking all the
> RAM on the computer.
>
> Since my map application is quite complex, I tried to create a very
> simple map to demonstrate this issue. I'm using setInterval to update
> marker position every 10 minutes in my prod. application, but I update
> every 10 seconds in my little example 
> here:http://www.canamgroup.ws/GM.nsf/Map4?OpenPage
>
> I just kept open this map for 30 minutes, and RAM went from ~60 megs to
> ~500 megs in IE !!
> As soon as I go to another page (or obviously close the browser), the
> RAM decrease normally.
>
> With Firefox, It went from ~50 megs to ~65 megs (it kept increasing and
> decreasing after each refresh).
>
> In V2, we had to use "GUnload()" to avoid memory issues. Is there
> something special I must do in V3?
> I read the documentation thoroughly and I thought I was doing all the
> right things (.setMap(null) and empty my array) as explained 
> here:http://code.google.com/apis/maps/documentation/javascript/overlays.ht...
>
> Can someone help?
> Thanks!

Try using "setTimeout" instead of "setInterval".  If your computer
cannot service interrupts quickly enough, you may be producing a flood
of interrupts.

For a simple example, see:

    http://www.polylib.us/polycluster/fixleak

CPU speed determines the pace.  It is also a good idea to use
"clearTimeout" or "clearInterval" to discard unserviced interrupts.

-- 
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.

Reply via email to