What you are seeing may be normal. The garbage collector does not
kick in immediately. The point at which it does kick in may be
different among browsers. It may depend on the size of the heap in
your particular configuration.
The reclaimed memory may never be returned to the heap but instead
saved for future allocations. Allocation requests will be filled
initially from reclaimed memory. If not enough is available and/or it
is too fragmented, additional memory must be allocated from the heap.
Once the equilibrium level is reached, memory usage ought to remain
stable.
If memory usage at the end of an hour is not significantly different
from memory usage at the end of a day, I do not believe you are
experiencing memory leaks. Just to be safe, I have made a change to
the test case. Instead of a large array of a lot of small {x:,y:}
objects, it is using a small {x:,y:} object of large arrays. It ought
to reduce fragmentation by keeping everything contiguous. The garbage
collector will have less work to do to coalese little fragments. The
actual workings of individual garbage collectors are only known by the
browser designers. What is important is for an application to be able
to run for a long time without crashing.
--
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.
