On Dec 3, 3:33 pm, John Mick <[email protected]> wrote:
> Okay so here is what I observed on your PolyCluster test:
>
> At 5:00PM EST on 12/2/2010:
> -Firefox was using about 52,000K of Memory (This number would
> increase quickly into a low 100,000K then lower itself back down to
> around 52,000K)
> -Google Chrome was using about 35,000K of Memory (This number was
> also increasing and then lowering itself back down to around 35,000K)
> -Internet Explorer 8 was using about 33,504K of Memory (Unlike
> Firefox and Chrome, this memory usage only fluctuated slighting around
> 33,504K)
>
> At 10:25AM EST on 12/3/2010:
> -Firefox was using about 168,000K of Memory (This number would
> increase very quickly to as high as 303,000K then reduce itself back
> down to a little higher than 168,000K)
> -Google Chrome was using 1,242,840K of Memory and steadily
> increasing - I never observed this to go back down
> -Internet Explorer 8 was using only 43,000K of Memory and was
> still only slightly fluctuating around that number
>
> It looks like the VML implementation in PolyCluster seems to work
> better than the SVG implementation - as far as memory usage goes.
> Unfortunately by now it has become obvious to me that I won't be able
> to use the Google Maps V3 Polygon objects and it seems that I'll have
> to continue to use a proprietary SVG/VML solution to keep my real-time
> application running.
>
> If I didn't have a requirement of this application remaining open in a
> web browser 24 hours a day, 7 days a week - these memory leaking
> issues wouldn't be such a huge concern of mine.
Thanks John,
At least nothing crashed, correct ?
Garbage collection is performed "Just-in-time". Perhaps you caught
Firefox & Chrome close to their high water marks. I will try to
figure out what I might be doing to leave debris.
Internally, the paths are stored as arrays rather than as objects. It
is machine friendly but not human friendly. Perhaps the little
{x:,y:} objects in the application itself are causing fragmentation of
the memory pool. I will experiment.
If you are successful, please let me know what you did. I will be
happy to share some of my code with you too. For what it is worth, I
am using CANVAS for Firefox & Chrome if neither "setClick()" nor
"setCover()" is called to establish event listeners. Otherwise, SVG
is used.
I have made a change to the test case to force the use of SVG where
appropriate. Be sure to clear your cache.
http://www.polylib.us/polycluster/fixleak
Let me know if it helps. Thanks again,
Berry
--
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.
