Hi, On 8/9/07, Steven M. Ottens <[EMAIL PROTECTED]> wrote: > I'm investigating the memory leak bug (http://jira.codehaus.org/ > browse/MAP-404) and already discovered that ButtonBase.js is creating > useless <img> elements which leak (lines 79 and 86). Since only the > src is required the createElement("IMG") can actually be skipped.
I agree. This is a remainder from pre-OpenLayers. > Still there are leaks with buttons. I noticed that OpenLayers has a > destroy function at certain places. OpenLayers also has onunload events that take care of destroying objects. > Any opinions? Ideas how to implement this or alternative ways to get > rid of leaking widget-DIVs? The question is: do we really need to care about memory leaks when unloading? IMO mapbuilder application are usually single-page applications, and if the page is unloaded, the user is finished and will maybe even close the browser. > Obviously this will be a large change and is meant for after the > release. Agreed, and IMHO this memory leak thing is not top priority. Regards, Andreas. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
