Hi, A known issue is that capabilities parsing is slower than it has to be. The memory consumption may be related to this. See http://trac.osgeo.org/openlayers/ticket/3187
Regards, Andreas. On Mar 8, 2011, at 21:33 , KevinGreen24 wrote: > I was recently working on some javascript code which took the text response > from a WMS Get Capabilities call and used OpenLayers' formatting to parse it > into an array of features: > > var CAPformat = new OpenLayers.Format.WMSCapabilities(); > var capabilities = CAPformat.read(wmsString); > > I've noticed that the call to .read causes a memory spike of 2-300 MB of > utilized web browser memory that does not get cleaned up, even if .destroy() > is called on the CAPformat object. I have made 3 consecutive calls to this > code and have seen Firefox.exe consume 1.2 GB of memory. Has anyone else > encountered this issue and have a resolution to it? > > FYI here's a URL i was testing against to make the get capabilities call: > http://giswebservices.massgis.state.ma.us/geoserver/wms > > Thank you, > > -KG > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/WMSCapabilities-parsing-causing-memory-spike-tp6140541p6140541.html > Sent from the OpenLayers Dev mailing list archive at Nabble.com. > _______________________________________________ > Dev mailing list > d...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/openlayers-dev -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers. _______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
