[OpenLayers-Users] Excessive memory use (memory leak) on Chrome?

[Worth Lutz]

  _____  

From: Worth Lutz [mailto:wal3 at mindspring.com] 
Sent: Friday, November 22, 2013 1:07 PM
To: 'mail.roliveira at gmail.com'
Subject: RE: [OpenLayers-Users] Excessive memory use (memory leak) on
Chrome?

 

I am pulling map data from my own wms server and am only showing tiles.

 

Using Windows task manager to see memory, my application starts out with
113,555k of memory.

By zooming and panning it quickly rises to something like 1,771,500k and
then Chrome chokes and goes "Aw, Snap" and I have to reload the page.

 

 

Worth

 

 

 

  _____  

From: mail.roliveira at gmail.com [mailto:mail.roliveira at gmail.com] 
Sent: Friday, November 22, 2013 11:44 AM
To: wal3 at mindspring.com; openlayers-users at lists.osgeo.org
Subject: RE: [OpenLayers-Users] Excessive memory use (memory leak) on
Chrome?

 

What do you mean by large memory? How much?

What map provider are you using? google? OSM?

Are you using SVG features?

I also notice some memory increase (up to 50MB) specially on zoom out that
causes an increase DOM Node Count and Event Listener Count. But eventually
it decreases to 30MB or bellow.

Sent from Alto - altomail.com

 

  _____  

From: wal3 at mindspring.com<wal3 at mindspring.com>
To: <openlayers-users at lists.osgeo.org>
Sent: Friday, November 22, 2013
Subject: [OpenLayers-Users] Excessive memory use (memory leak) on Chrome?

I'm having a problem with large memory use in Chrome and eventually Chrome
crashes with the web page failed.

All I'm doing is zooming in and out and panning to refresh tiles as I change
styles in the mapfile.

Could this be a problem in OpenLayers? I'm using OpenLayers 2.13.

Thanks,

Worth

  _____  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3629/6854 - Release Date: 11/21/13

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-users/attachments/20131122/48ff64e3/attachment-0001.html>