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.
On Dec 2, 5:05 pm, John Mick <[email protected]> wrote:
> Ah excellent - it looks like PolyCluster is a lot similar to the same
> solution I had to write for my V2 app - at a quick glance PolyCluster
> looks nice!. I made a SVG/VML library that managed the creation of
> the Vector objects on a Custom Overlay and handled pretty much
> everything manually. I was hoping to avoid having to do that again -
> leveraging V3 - but it is starting to look like I won't be able to
> from this point.
>
> I'm heading out of the office now - I'm going to leave your test page
> open on the same browsers I mentioned testing earlier, IE 8, Chrome,
> and FF, overnight and I'll let you know what I find in the morning.
>
> Thanks for the information!
>
> On Dec 2, 4:40 pm, bratliff <[email protected]> wrote:
>
>
>
>
>
>
>
> > On Dec 2, 8:16 pm, John Mick <[email protected]> wrote:
>
> > > I'm not sure if using MVCArrays are going to solve this issue.
>
> > > Consider the nature of my program will have an entirely new set of
> > > LatLng points every 25 seconds or so. None of the points in the multi-
> > > dimensional MVCArray will be reused. I do not see any way to remove
> > > all of the values inside the existing MVCArrray object and recreate
> > > them without throwing a ton of redraw events - which essentially hangs
> > > the browser in one shot.
>
> > > I'm not sure if I'm missing it, but I haven't found much information
> > > on the behavior of this MVCObjects either - I'm not sure that this is
> > > the type of solution I am looking for.
>
> > The only reason I can see to ever use MVC arrays with polys is for
> > interactive editing. It is inherently inefficient. Otherwise, it is
> > just extra bloat. Perhaps I am missing another use for it.
>
> > I have built a simple test using PolyCluster:
>
> > http://www.polylib.us/polycluster/fixleak
>
> > I have run it in Firefox for over an hour without crashing. I have
> > not tested it in other browsers.
--
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.
