Ticket #369 (new task)

Opened 6 years ago

Last modified 4 years ago

Thorough Review of OpenLayers Memory Management

Reported by: euzuro Owned by: euzuro sde
Priority: major Milestone: Maintenance
Component: general Version:
Keywords: Cc:
State:

Description

Need to sift through the code and make sure all object creation and deletions are in order, as well as event registerings and unregisterings.

Specifically, for every time a call is made to new, there should be a corresponding call to the object's destroy().

same goes for event.register() and event.unregister()

also we should consider adding a function removeFromMap() that would be the counter to setMap(), which would be the convenient place to register/unregister map events.

Change History

Changed 5 years ago by euzuro

  • milestone set to 2.3 Release

Changed 5 years ago by euzuro

  • owner set to euzuro sde

Changed 5 years ago by euzuro

  • milestone changed from 2.3 Release to 2.4 Release

Changed 5 years ago by openlayers

  • keywords review added

patch added as per  http://www.nabble.com/Markers%27-events-memory-leak--tf3232599.html

stopObservingElement method added to Event object; stopObservingElement call added to Icon's destroy method;

Changed 5 years ago by sderle

  • milestone changed from 2.4 Release to 2.5 Release

Changed 5 years ago by crschmidt

  • keywords review removed

Changed 5 years ago by euzuro

  • milestone changed from 2.5 Release to Maintenance

Changed 5 years ago by camerons

To search for memory leaks, Drip is reported to be useful.  http://outofhanwell.com/ieleak/index.php?title=Main_Page

Changed 4 years ago by openlayers

sIEve is an extended version of Drip.
Can be found here:  http://home.wanadoo.nl/jsrosman/

Note: See TracTickets for help on using tickets.