24806 2009-03-25 10:37:43 -0700 addEventListener to node with closure+circular ref leaks DOM nodes 2009-04-11 12:54:23 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) All All UNCONFIRMED P2 Normal --- 0 280lifestyle webkit-unassigned ddkilzer emacemac7 ggaren pam oldest_to_newest 115175 0 280lifestyle 2009-03-25 10:37:43 -0700 The following JS leaks DOM nodes until the document is thrown away. Safari 4, also tested with Chrome 1.x/v8 which shows the same behavior. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <title>listTest</title> <script type="text/javascript" charset="utf-8"> makeClosure= function(object) { return function() { return object; } }; gIntervalCount = 0; myLeakyFunc = function() { var i, widget; console.log("myLeakyFunc: "+gIntervalCount++); for(i=0; i<1000; i++) { // The leak seems to be caused by an event listener on a node, // where the listener's closure has a circular reference to the node. widget = document.createElement('div'); widget.addEventListener('whatever', makeClosure(widget), false); // Adding some extra chold nodes to the leaked div makes the memory leak more apparent, but is not necessary. widget.innerHTML = '<div></div><div></div><div></div><div></div><div></div><div></div><div></div><div></div>'; } } window.setInterval(myLeakyFunc, 500); </script> </head> <body> </body> </html> 115176 1 280lifestyle 2009-03-25 10:38:17 -0700 Does not leak in Firefox 3.x 115234 2 ddkilzer 2009-03-25 15:14:03 -0700 Looks like a duplicate of Bug 21260. 116675 3 ddkilzer 2009-04-06 15:10:08 -0700 Geoff, was this fixed by Bug 21260? http://trac.webkit.org/changeset/42256